You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go to the call page in a window of 600px width or greater.
Press ⌘ + F5 to start VoiceOver.
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.
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.
The text was updated successfully, but these errors were encountered:
Steps to reproduce
⌘ + F5
to start VoiceOver.^⌥→
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.
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.The text was updated successfully, but these errors were encountered: