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

Implicit aria semantics for <th> with set scope attribute #495

Open
jlp-craigmorten opened this issue Nov 11, 2023 · 0 comments
Open

Implicit aria semantics for <th> with set scope attribute #495

jlp-craigmorten opened this issue Nov 11, 2023 · 0 comments

Comments

@jlp-craigmorten
Copy link

According to html-aam:

If scope="row" then map th to rowheader
If scope="col" then map th to columnheader

REF: https://www.w3.org/TR/html-aam-1.0/#att-scope

Should this be reflected in the conformance requirements of html-aria for the implicit aria semantics for the <th> element as something user-agents are expected to map implicitly for accessibility APIs? Currently it states:

role=columnheader, rowheader or cell if the ancestor table element is exposed as a role=table

role=columnheader, rowheader or gridcell if the ancestor table element is exposed as a role=grid or treegrid

No corresponding role if the ancestor table element is not exposed as a role=table, grid or treegrid

REF: https://www.w3.org/TR/html-aria/#docconformance-attr

I.e. update to something like:

role=columnheader, rowheader or cell if the ancestor table element is exposed as a role=table

role=columnheader, rowheader or gridcell if the ancestor table element is exposed as a role=grid or treegrid

role=rowheader if the th element has attribute scope=row

role=columnheader if the th element has attribute scope=column

No corresponding role if the ancestor table element is not exposed as a role=table, grid or treegrid

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

No branches or pull requests

1 participant