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
I verified there's no existing issue for this bug.
There are no existing issues
Current behavior
The expressive progress bar module features an ARIA live region (role="status") that announces rotating messages to screen readers.
All Skin component docs are compiled into a single HTML page, so the expressive progress bar docs and examples are rendered any time you visit the Skin docs. This means that when perusing the docs with a screen reader, you always hear the expressive progress bar messages. This can be distracting, especially when exploring other components' docs.
Expected behavior
In the docs, the expressive progress bar code examples should include role=status markup, but the actual rendered examples should not.
Skin version
No response
Device/OS/Browser info
No response
Steps to reproduce
1. Turn on a screen reader.
2. Navigate to https://opensource.ebay.com/skin/
3. Be reminded every second and a half that your order is almost ready.
Relevant code block
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I verified there's no existing issue for this bug.
Current behavior
The expressive progress bar module features an ARIA live region (role="status") that announces rotating messages to screen readers.
All Skin component docs are compiled into a single HTML page, so the expressive progress bar docs and examples are rendered any time you visit the Skin docs. This means that when perusing the docs with a screen reader, you always hear the expressive progress bar messages. This can be distracting, especially when exploring other components' docs.
Expected behavior
In the docs, the expressive progress bar code examples should include role=status markup, but the actual rendered examples should not.
Skin version
No response
Device/OS/Browser info
No response
Steps to reproduce
Relevant code block
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: