Accessible name updates #42691
Open
Accessible name updates #42691
+18
−11
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
github-actions
bot
added
Content:CSS
Contributor
|
Preview URLs Flaws (1)URL:
External URLs (1)URL:
(comment last updated: 2026-01-09 14:12:34) |
scottaohara
approved these changes
Jan 8, 2026
Accidentally wiped a `content: "";` and have restored it.
estelle
reviewed
Jan 8, 2026
Member
estelle
left a comment
estelle
left a comment
There was a problem hiding this comment.
Looks good. Thank you. i made some linking, i18l, and future-proofing suggestions.
I didn't reference images because the example used a symbol, not an image. That said, happy to use this language. I expect readers will understand the difference. Co-authored-by: Estelle Weyl <[email protected]>
estelle
reviewed
Jan 9, 2026
Co-authored-by: Estelle Weyl <[email protected]>
Contributor
Author
|
@estelle Thanks for the edits. All accepted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Addresses incorrect or absent guidance related to accessible names in the Creating CSS carousels guide.
Motivation
Devs are starting to try to implement these and creating WCAG violations without realizing it because this, along with lots of promotion in dev sites, wrongly claims these are "accessible" (without qualifying how or in what way).
Additional details
Recent evidence of their baseline inaccessibility: https://www.sarasoueidan.com/blog/css-carousels-accessibility/
Related issues and pull requests
Fixes #39125