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

Screen reader users can access the report pane before a call has ended #264

Open
henrycatalinismith opened this issue Sep 24, 2022 · 0 comments

Comments

@henrycatalinismith
Copy link

henrycatalinismith commented Sep 24, 2022

Steps to reproduce

  1. Go to the call page in a window of 600px width or greater.
  2. Press ⌘ + F5 to start VoiceOver.
  3. Use ^⌥→ to move focus beyond the end of the input pane.

Expected outcome

No more panes are possible to access using plain mouse and keyboard input so none should be available in VoiceOver either.

Actual outcome

It's possible to interact with the report pane in VoiceOver during the call.

macOS VoiceOver screen recording where we escape into a hidden part of the UI

As the report pane only makes sense to access after a call has concluded, being able to access it with assistive technology during an ongoing call falls under WCAG 2.4.3 Focus Order because the focus order doesn't preserve meaning. WCAG 1.3.1 Info and Relationships may also be applicable as the hidden state of the report pane's presentation isn't available programmatically to assistive technology.

Recommendation

It seems like this UI is rendered before it's needed to facilitate the nice slide transition when it appears. One option could be to live without the animation. Another could be to try setting the pane to inert until it appears.

This issue is effectively a duplicate of #104, as this is the same bug reported there except with a slightly wider scope. The fix for that original issue was to disable tab keypresses entirely, and fixing #263 will walk back that original fix. Addressing this issue in a way that covers screen reader usage as well as plain old tab navigation will unblock implementing the recommendations for #263.

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

No branches or pull requests

1 participant