Open reitermb opened 1 year ago
@jtimpe is this still needed? If still relevant, let's place it into an epic.
@jtimpe is this still needed? If still relevant, let's place it into an epic.
This / other a11y tickets that are still open should all be up to date & still needed.
Epic wise this is another where it doesn't fit cleanly into our epics. This is tech-debt-y
Description
While the user cannot tab outside of the dialogs (e.g. mobile nav menu, timeout dialog, infinite request dialog), they can "read" outside using arrow key based navigation modes of screenreaders. This results in potentially confusing experiences for affected users.
Testing steps
Trigger a timeout/infinite request dialog Open a screenreader Use arrow key navigation to read through the contents of the dialog and then note whether items outside the dialog are read
Suggested fix
The likely fix here is likely related to developing contextual tab-index / aria property values depending on whether a dialog element is activated. It may also be feasible to re-order the page structure to accomplish the same thing.
Notes
It's also possible that this is under the umbrella of issues that will be corrected by the USWDS version bump #2307 will implement. We should re-test once that work is merged to confirm whether this is a distinct issue.
Modal dialogues address tab behavior by intercepting keyboard events - see
Modal
element. Should scroll through all elements presented within the modal (block out elements underneath)