-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[a11y]: FileUploaderDropContainer component has critical violation "The tabbable element's role 'none' is not a widget role" #12498
Comments
From looking at the component code, maybe the fix is to move the |
Also, can the fix for this issue be backported to carbon v10 alongside v11? Thanks |
hi, am also facing this issue in one of our applications. Any update on this? |
will this fix be available on v10? |
We need to port this back to v10 |
Hi, |
Closed via #14517, will be included in the next release of V10 |
Package
carbon-components-react
Browser
Chrome
Operating System
MacOS
Package version
7.56.0
React version
17.0.2
Automated testing tool and ruleset
IBM Equal Access Accessibility Checker - Latest Deployment
Assistive technology
No response
Description
The
FileUploaderDropContainer
component has a critical a11y violation"The tabbable element's role 'none' is not a widget role"
that was found in our product using the IBM Accessibility Checker tool and is re-producible on the v10 and v11 storybook as well.v10 storybook
v11 storybook
WCAG 2.1 Violation
No response
Reproduction/example
Carbon v10 storybook - https://v7-react.carbondesignsystem.com/?path=/story/components-fileuploader--drag-and-drop-upload-container-example-application and/or Carbon v11 storybook - https://react.carbondesignsystem.com/?path=/story/components-fileuploader--drag-and-drop-upload-container-example-application
Steps to reproduce
On the storybook link (either v10 or v11) for the FileUploader -> FileUploaderDropContainer story, run the IBM Accessibility Checker scan. The scan should report the critical violation mentioned above (scroll to the bottom of the violations list).
Code of Conduct
The text was updated successfully, but these errors were encountered: