-
Notifications
You must be signed in to change notification settings - Fork 26
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
HTML-AAM: Unnamed <section> should map as <div>, not unconditionally as role="region" #79
Comments
@stevefaulkner, @joanmarie, @klown As per the commit above, see revised mappings for Will merge branch if you're happy. |
@jasonkiss Looks good to me. |
Please merge this branch. We are writing the test harness and need this to be merged. |
Merged. 2d740ef |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Raising this issue based on comments by myself, @joanmarie, @mcking65, and @matatk from w3c/aria#513.
There, the mapping of ARIA role="region" is conditional on the element having an accessible name. If not, the AAPI role reverts on the native role of the element.
The HTML-AAM unconditionally maps
<section>
toregion
, except in the case of UIA. The suggestion in w3c/aria#513 is to map unnamed<section>
as if it was a<div>
.Heads up to @richschwer, since you are reviewing the HTML-AAM.
The text was updated successfully, but these errors were encountered: