Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call log modal focus order differs from visual order #270

Open
henrycatalinismith opened this issue Oct 15, 2022 · 0 comments · May be fixed by #281
Open

Call log modal focus order differs from visual order #270

henrycatalinismith opened this issue Oct 15, 2022 · 0 comments · May be fixed by #281

Comments

@henrycatalinismith
Copy link

Steps to reproduce

  1. Open an assignment.
  2. Click the log button.
  3. Press ⌘ + F5 to start VoiceOver.
  4. Focus the close button.

Expected outcome

The close button is visually first so it should be first in the focus order. See C27: Making the DOM order match the visual order for details of the success criteria this addresses and the assistive technology use cases it supports.

Actual outcome

The close button is at the end of the focus order despite being at the top left of the screen.

VoiceOver focusing the close button at the end of the focus order

Severity

The success criterion covering this issue is WCAG level A – the minimum level. Most organizations aim for a conformance level of AA, which includes all level A criteria. In this particular case this issue seems unlikely to seriously hamper anybody's work but as it's level A it's still moderately severe.

Recommendation

Rearrange the DOM order so that .OverlayStack-closeButton is before .OverlayStack-overlay. In React terms: just render the close button first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant