We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Our current progress bar implementation defaults to using a div and span and adding aria roles for accessibility.
We should use native html elements when possible for better accessibility.
Replace the progress component with the native element and add styles as needed
All users, especially those using accessibility tools
The current implementation works fine and does resolve most accessibility issues with aria attributes.
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/progressbar_role https://developer.mozilla.org/en-US/docs/Web/HTML/Element/progress
The text was updated successfully, but these errors were encountered:
I believe this will require an update to the UI kit in order for the styling to take effect on the progress element.
Sorry, something went wrong.
nylon22
No branches or pull requests
🚀 Feature request
Current Behavior
Our current progress bar implementation defaults to using a div and span and adding aria roles for accessibility.
Desired Behavior
We should use native html elements when possible for better accessibility.
Suggested Solution
Replace the progress component with the native element and add styles as needed
Who does this impact? Who is this for?
All users, especially those using accessibility tools
Describe alternatives you've considered
The current implementation works fine and does resolve most accessibility issues with aria attributes.
Additional context
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/progressbar_role
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/progress
The text was updated successfully, but these errors were encountered: