-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(material/chips): remove button role from editable chips #27317
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
Conversation
Deployed dev-app for 4e2cf9c to: https://ng-dev-previews-comp--pr-angular-components-27317-9f8cfdw6.web.app Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt. |
dd43095
to
b056fc2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Removes the button role from editable input chips. Fix accessibility issue in ChipRow where the chip action element is mislabeled as a button (angular#27106). Remove butotn role by remove DOM node thtat used to have button role and using the gridcell role element for the primary chip action instead. Tested cross-browser with supported screen readers on MacOS and Windows. Tested on "Chips with input" example by verifying that a chip could be added then edited after adding. Also verifying that AT read the chip's aria description. Testing Environment - macOS 13.4 (22F66) / VoiceOver - Chrome Version 114.0.5735.133 (Official Build) (arm64) - Firefox 114.0.1 (64-bit) - windows 10 Enteprise Version 22H2 - JAWS VERSION 2020.2006.12 ILM - NVDA version 2022.3 - Chrome Version 114.0.5735.134 (Official Build) (64-bit) - Firefox 114.0.2 (64-bit) Fix angular#27106
b056fc2
to
4e2cf9c
Compare
I'm merging this PR since the related CL was submitted yesterday. |
Removes the button role from editable input chips. Fix accessibility issue in ChipRow where the chip action element is mislabeled as a button (#27106). Remove butotn role by remove DOM node thtat used to have button role and using the gridcell role element for the primary chip action instead. Tested cross-browser with supported screen readers on MacOS and Windows. Tested on "Chips with input" example by verifying that a chip could be added then edited after adding. Also verifying that AT read the chip's aria description. Testing Environment - macOS 13.4 (22F66) / VoiceOver - Chrome Version 114.0.5735.133 (Official Build) (arm64) - Firefox 114.0.1 (64-bit) - windows 10 Enteprise Version 22H2 - JAWS VERSION 2020.2006.12 ILM - NVDA version 2022.3 - Chrome Version 114.0.5735.134 (Official Build) (64-bit) - Firefox 114.0.2 (64-bit) Fix #27106 (cherry picked from commit e0608cb)
Thanks, my bad 🤦 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
fix(material/chips): remove button role from editable chips
Removes the button role from editable input chips. Fix accessibility
issue in ChipRow where the chip action element is mislabeled as a
button (#27106). Remove butotn role by remove DOM node thtat used to
have button role and using the gridcell role element for the primary
chip action instead.
Tested cross-browser with supported screen readers on MacOS and Windows.
Tested on "Chips with input" example by verifying that a chip could be
added then edited after adding. Also verifying that AT read the chip's
aria description.
Testing Environment
Fix #27106