act-rules / act-rules.github.io

Accessibility conformance testing rules for HTML
https://act-rules.github.io/
Other
131 stars 67 forks source link

Rule idea: A non-global WAI-ARIA state or property is used where it is not supported #2189

Closed giacomo-petri closed 1 month ago

giacomo-petri commented 1 month ago

Following yesterday's discussion in the ARIA Working Group regarding https://github.com/w3c/aria/issues/2168:

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

, it should not be exposed in MSAA implementations as STATE_SYSTEM_CHECKED.

there's an agreement to advance towards making it an author requirement as well.

Presently, test tools inconsistently flag these scenarios. Establishing a rule for this would be helpful, given ARIA's forthcoming clarification regarding author responsibilities.

I'm willing to handle this task if the group is in agreement to proceed with implementing the rule.

giacomo-petri commented 1 month ago

Note: It will closely resemble the proposed rule https://www.w3.org/WAI/standards-guidelines/act/rules/5c01ea/proposed/.

Most likely, we just need to revise and tweak the two expectations, including "non-global WAI-ARIA state or property" and changing the second one from "prohibited" to "prohibited or not supported," including additional passing and failing examples.

The remainder of the rule already addresses the essence of the "new requirement."

I'm uncertain whether we should adjust the existing proposal or suggest an entirely different rule. However, if we opt for the latter, we'll also need to modify the title of the proposed rule.

giacomo-petri commented 1 month ago

My fault; this rule already covers the necessary checks. Closing