• Modal using native showModal lets users tab out to address bar, challenging old focus‑trap rule. • WCAG spec never mandates trapping focus inside dialogs; guidance is outdated. • Earlier docs advised focus limits before inert attribute and native dialog existed. • Native dialog and inert attribute simplify accessibility, removing need for manual focus management. • Screen readers can legitimately move focus to browser chrome, like address bar. • Modern best practice: rely on native features, not custom focus trapping.

Article Summaries:

  • Recent discussions on the Web Accessibility Community Group have clarified that focus trapping is no longer required for native <dialog> elements using the showModal() method. WCAG does not mandate trapping focus within a dialog, and the Accessible Rich Internet Applications (ARIA) Authoring Practices were written before the inert attribute and native dialog support were common. The APA Working Group confirmed that the current behavior-allowing users to tab from a modal to browser chrome or the address bar-is acceptable and even beneficial for keyboard users and kiosk scenarios. Consequently, developers can rely on the native dialog API without implementing custom focus‑trap logic.

Sources: