"Accessibility Supported" might benefit from mentionning accessibility APIs

[A11yTea]

Hi everyone,

I filed an issue for WCAG-EM that might impact WCAG, its why I want to also post it here. "Accessibility Supported" and Accessibility APIs... #150.

To summarize, I want to inquire if accessibility supported should make mention of accessibility APIs. Especially since if technologies build to the APIs rather than specific assistive technology, it allows for more support for all other assistive technologies.

I know 4.1.2 Name, Role, Value supports accessibility APIs but since they are central to interoperability, I want to know if content should be added to explain those APIs in the Accessibility Supported section.

[patrickhlauke]

Moving to discussion for now, as I don't believe this will be addressed (at least not quickly) in WCAG 2.x

Also, the concept of "accessibility supported" certainly includes, but isn't limited to, accessibility APIs (or even AT themselves). something may be "accessibility supported" when it pertains to generally available browser/OS settings, or even just "it can be activated with a 'regular' keyboard", or similar.

[A11yTea]

@patrickhlauke Unfortunately, once a topic is moved to discussion, its the end of the conversation. Might as well close this.