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
We use the audio player library to play a variety of media fields and recently received feedback from a third-party accessibility vendor that the tab ordering of the layout we implemented (Horizontal Reverse) is incorrect.
For context, below is the tab order of the 'Stacked' layout, which would pass an accessibility scan (please note that 1 in each image below represents the container itself, which is good:
When in contrast, the 'Horizontal Reverse' layout has a tab order of the following:
Checking the other layouts, it looks like the same 'elements' within each layout are assigned the same tab order, when in fact it should be in a logical order based upon what is shown.
For additional context, the following WCAG rules are currently impacted by this:
2.4.3 - Focus Order
F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability
F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order
It'd be great if this could either be fixed to accurately represent each different layout or if we'd have the ability to change the tab order ourselves through the library.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello!
We use the audio player library to play a variety of media fields and recently received feedback from a third-party accessibility vendor that the tab ordering of the layout we implemented (Horizontal Reverse) is incorrect.
For context, below is the tab order of the 'Stacked' layout, which would pass an accessibility scan (please note that 1 in each image below represents the container itself, which is good:
When in contrast, the 'Horizontal Reverse' layout has a tab order of the following:
Checking the other layouts, it looks like the same 'elements' within each layout are assigned the same tab order, when in fact it should be in a logical order based upon what is shown.
For additional context, the following WCAG rules are currently impacted by this:
It'd be great if this could either be fixed to accurately represent each different layout or if we'd have the ability to change the tab order ourselves through the library.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions