Focus Trap vs Native Restoration in Jira Align Modals

Goal: Preserve Keyboard Navigation Integrity in Jira Align Modals

When users open a modal dialog, the interface must keep focus inside the dialog until it is closed. Currently, Jira Align’s modal implementation relies on native browser focus restoration, which can fail when the dialog’s content is injected dynamically or the opener element is removed from the DOM. This leads to focus loss and disrupts keyboard‑only navigation.

The unresolved decision is whether to adopt a comprehensive focus‑trap strategy for every modal (using ARIA attributes and JavaScript focus management) or to continue with the lighter native approach. Each option has trade‑offs in terms of implementation complexity, performance, and compatibility with existing customizations.

What are the implications of adding a focus trap to all Jira Align modals for keyboard‑only users? Does the native focus restoration suffice for dynamic content scenarios, or does it risk accessibility violations? How might a focus trap affect the performance and customization layers already present in Jira Align?