docs(material/chips): require announcing removal of chip to AT #27197
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zarend
added
Accessibility
|
Deployed dev-app for 814f28e to: https://ng-dev-previews-comp--pr-angular-components-27197-z8zwt8el.web.app Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt. |
jelbourn
reviewed
Jun 8, 2023
Update the accessibility instructions for the `MatChipRemove` directive. Require author to communicate to Assisstive Technology when a chip is removed. This can be done by sending a message with `LiveAnnouncer`. Following these instructions avoids an a11y issue where removing a chip is communicated only visually, and it is not communicated with any other senses (angular#12122). Update all examples to follow these instructions by announcing deletion with `LiveAnnouncer`. Fix angular#12122
zarend
force-pushed
the
remove-chip-a11y-docs
branch
from
81e84f9 to
814f28e
Compare
zarend
added a commit
that referenced
this pull request
Jun 9, 2023
Update the accessibility instructions for the `MatChipRemove` directive. Require author to communicate to Assisstive Technology when a chip is removed. This can be done by sending a message with `LiveAnnouncer`. Following these instructions avoids an a11y issue where removing a chip is communicated only visually, and it is not communicated with any other senses (#12122). Update all examples to follow these instructions by announcing deletion with `LiveAnnouncer`. Fix #12122 (cherry picked from commit cddb04f)
zarend
added a commit
that referenced
this pull request
Jun 9, 2023
Update the accessibility instructions for the `MatChipRemove` directive. Require author to communicate to Assisstive Technology when a chip is removed. This can be done by sending a message with `LiveAnnouncer`. Following these instructions avoids an a11y issue where removing a chip is communicated only visually, and it is not communicated with any other senses (#12122). Update all examples to follow these instructions by announcing deletion with `LiveAnnouncer`. Fix #12122 (cherry picked from commit cddb04f)
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the accessibility instructions for the
MatChipRemovedirective. Require author to communicate to Assisstive Technology when a chip is removed. This can be done by sending a message withLiveAnnouncer.Following these instructions avoids an a11y issue where removing a chip is communicated only visually, and it is not communicated with any other senses (#12122).
Update all examples to follow these instructions by announcing deletion with
LiveAnnouncer.Fix #12122