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
[4.1.1] Ion-checkbox's internal button does not have an accessible name #17796
Comments
I would like to pick this up as this is a beginner friendly fix. |
Same as |
This issue has been labeled as If you'd like to work on this issue, please comment here letting us know that you would like to submit a pull request for it. This helps us to keep track of the pull request and make sure there isn't duplicated effort. For a guide on how to create a pull request and test this project locally to see your changes, see our contributing documentation. Thank you! |
Bug ionic-team#17796 The issue creator mentiones that there is an option missing to create an aria-label for the button. Add an ariaLabel prop to the checkbox and delegate it to the button for accessibility. closes ionic-team#17796
…een readers (ionic-team#22402) fixes ionic-team#21644 fixes ionic-team#20517 fixes ionic-team#17796
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Bug Report
Ionic version:
[x] 4.1.1
Current behavior:
Ion-checkbox's button does not have an accessible name.
Expected behavior:
Ion-checkbox should allow a prop named aria-label and set it on Ion-checkbox's internal button.
Steps to reproduce:
Use Ion-checkbox in a simple html and run Lighthouse Audit from Chrome.
It shows the following error for accessibility :
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers.
Failing Elements
<button type="button"></button>
Ionic info:
The text was updated successfully, but these errors were encountered: