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.
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
Utilize
aria-describedby
on allActionList
descriptions #4666Utilize
aria-describedby
on allActionList
descriptions #4666Changes from 8 commits
d8cd733
377ef5d
6c00d25
26800fb
69a57f1
a672887
5fad1fd
c62806e
3b4f8c0
9dbc082
57a5034
0b11bc6
baf63b7
cf00630
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Re: moving inline description from label to description, can we create a different PR for that because I'm less confident about that change. (I brought inline description from aria-describedby to aria-label #1599 after an accessibility review 😅)
I see from https://github.com/github/primer/issues/2501#issuecomment-1674987399,
This is really old, so forgive me for missing the details, but I think inline description was assumed to be short and label-like, which block description is for longer and even multi-line text. It's not mentioned in the design docs, so I wonder if primer-designers have thoughts on this as well
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.
I've added it as a label via
aria-labelledby
instead of a description because if there's text content within trailing visual, it's usually short and connects directly to the main item's text (accessibl, e.g.Accessible name would be: "Tokens Available 8".
I mainly based this on examples I've seen in the wild. If we added it as a description, there's a chance it might be ignored, so I think
aria-labelledby
is a fair bet.I'd say it's very unlikely, since any text within the trailing visual isn't attached to
ActionList.Item
's accessible name/description currently.Yup that's fair! I think it's worth its own discussion to see if we'd want to switch it or not, as it definitely works both ways, as part of the accessible name, or as part of the description. I'll take that change out of this PR and create another so that we can discuss/see if we want to include it or not!
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.
Should now only include the proposed changed for
TrailingVisual
!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.
Does this also include within menus/selectpanels?
(Happy to go ahead with this, either of label vs description is better than aria-hidden i guess)