Skip to content
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

Mapping unnamed <section> element to role=generic #474

Closed
jlp-craigmorten opened this issue Jun 25, 2023 · 1 comment · Fixed by #475
Closed

Mapping unnamed <section> element to role=generic #474

jlp-craigmorten opened this issue Jun 25, 2023 · 1 comment · Fixed by #475

Comments

@jlp-craigmorten
Copy link

jlp-craigmorten commented Jun 25, 2023

Follows on from w3c/html-aam#346 (w3c/html-aam#348).

There have been prior changes in html-aam to update the mapping of the <section> element with no accessible name to role=generic.

Filing this for consideration to make the equivalent changes to the html-aria spec for the role mapping definition of the <section> element for consistency - moving from "no corresponding role" to "generic" in the no accessible name scenario.

Pertinent areas:

@jlp-craigmorten
Copy link
Author

Re-reading the issues, may be a duplicate of #365

scottaohara added a commit that referenced this issue Jun 26, 2023
closes #474

changes ref of section element without name from 'no corresponding role' to `role=generic`.

other changes made in this PR:
- remove duplicate instances of code elements from ARIA roles (mostly instances of role=generic).
- clarification for section element allowed roles - role=region not recommended in general, not just if the element is named since using the role w/out naming would be useless.  mention authors SHOULD NOT use role=generic on the element, per the change from no corresponding role.
scottaohara added a commit that referenced this issue Jun 26, 2023
closes #474

changes ref of section element without name from 'no corresponding role' to `role=generic`.

other changes made in this PR:
- remove duplicate instances of code elements from ARIA roles (mostly instances of role=generic).
- clarification for section element allowed roles - role=region not recommended in general, not just if the element is named since using the role w/out naming would be useless.  mention authors SHOULD NOT use role=generic on the element, per the change from no corresponding role.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant