-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
Update implicit ARIA roles according to spec changes #29546
Conversation
Implements changes from w3c/html-aria#425
Implements change from w3c/html-aria@ba30b83
Implements changes from w3c/html-aria#392
<code><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/form_role">form</a></code> if the form has an | ||
<a href="https://www.w3.org/TR/accname-1.1/#dfn-accessible-name">accessible name</a>, otherwise | ||
<a href="https://www.w3.org/TR/html-aria/#dfn-no-corresponding-role">no corresponding role</a> | ||
<code><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/form_role">form</a></code> |
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.
While this condition got removed in the spec, there's now a note saying quite the same thing in the cell next to it.
Removed it anyway for the sake of completeness, but I'd like someone to verify if it's alright or what should be done instead.
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.
added #29636 to address this.
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.
Wow. Thank you. Congratulations on your first merged MDN content PR. That is a large effort for a first PR! Welcome to the team!
Description
spec changes
Motivation
I was in a small argument about
<blockquote>
. got surprised that it doesn't have any implicit ARIA role. checked the spec, the spec says it actually assigns a role for it. duh confused, think i should do something about it. in the meantime i'll check if anything else needs updating... ohooohhhh motivation,,,
To stay up to date with the spec! :3
Additional details
Related issues and pull requests
Didn't touch
<summary>
element as there's already #28602 openedbeing sleepy and not knowing what to write in pr templates doesn't end well. sry