w3c / aria

Accessible Rich Internet Applications (WAI-ARIA)
https://w3c.github.io/aria/
Other
624 stars 118 forks source link

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 1 month ago

spectranaut commented 1 month ago

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: https://github.com/dequelabs/axe-core/issues/4433 I made an issue for VNU even though I can't find the authors must statement: https://github.com/validator/validator/issues/1716

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

spectranaut commented 1 month ago

Reading @WilcoFiers's discussion of axe-core in this comment makes me wonder about whether they would be unhappy with this change: https://github.com/w3c/aria/issues/1990#issuecomment-1663841058

spectranaut commented 1 month ago

Discussed in: https://www.w3.org/2024/05/09-aria-minutes.html#t09