-
Notifications
You must be signed in to change notification settings - Fork 126
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
[accname] Explicitly state UAs must ignore “aria-label” for slots #2385
base: main
Are you sure you want to change the base?
Conversation
This change updates the AriaLabel substep of the “Computation steps” section of the “Accessible Name and Description Computation” spec to explicitly state that the step must not be performed if the node being visited is a slot element.
✅ Deploy Preview for wai-aria ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Apologies, this one slipped off my radar. This does indeed LGTM 👍
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.
Agree with this addition, it's the correct framing.
I added a link above to the existing WPT tests for accname on slots... See tests 3 and 4. If more tests are needed, please file a new issue on interop-accessibility. Thanks Mike! |
This change updates the AriaLabel substep of the “Computation steps” section of the accname spec to explicitly state that the step must not be performed if the node being visited is a
slot
element.See the discussion at w3c/accname#173. It seems a requirement to ignore the
aria-label
attribute in this case — or to ignore any ARIA attributes present onslot
elements — may follow from normative requirements stated in some other spec.Nevertheless, a specific requirement should be stated at point of use in the text for this step in accname spec itself.
Test, Documentation and Implementation tracking
Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.