You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Rule 5 in CORE-AAM's State and Property Mapping General Rules says:
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#1716Proposal: add an
authors must not
statement here: https://w3c.github.io/aria/#supportedStateThe text was updated successfully, but these errors were encountered: