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

CORE-AAM has "user agents must not expose non-global, not support attributes on roles", but there is no related author error in ARIA? #2168

Open
spectranaut opened this issue Apr 26, 2024 · 2 comments
Assignees

Comments

@spectranaut
Copy link
Contributor

spectranaut commented Apr 26, 2024

Rule 5 in CORE-AAM's State and Property Mapping General Rules says:

Some WAI-ARIA properties are not global, and are only supported on certain roles. If a non-global WAI-ARIA state or property is used where it is not supported, user agents SHOULD NOT map the given WAI-ARIA property to the platform accessibility API. For example, if aria-checked="true" is specified on <div role="grid">, it should not be exposed in MSAA implementations as STATE_SYSTEM_CHECKED.

Seems like if we are requiring that browsers do not surface this information, then we should have an author error about adding it. Axe raises and error when this happens, although VNU doesn't raise any errors.

Here is the issue for Axe where I noticed this: dequelabs/axe-core#4433
I made an issue for VNU even though I can't find the authors must statement: validator/validator#1716

Proposal: add an authors must not statement here: https://w3c.github.io/aria/#supportedState

@spectranaut
Copy link
Contributor Author

Reading @WilcoFiers's discussion of axe-core in this comment makes me wonder about whether they would be unhappy with this change: #1990 (comment)

@spectranaut
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants