Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553)

> Authors may want to create an entirely new custom control for which there is no role in ARIA that fits. Should we follow the UIA model and define scripted control patterns, accompanied by a localized role name for the widget? 

I'm not sure what the UIA model is, but I've been impressed with https://github.com/a11y-api/a11y-api/ as a way of solving this problem.

On the latter question, maybe you could clear something up for me. How does accessibility technology deal with novel widget names? My understanding from reading https://w3c.github.io/aria/html-aam/html-aam.html#html-element-role-mappings is that there is a predefined set of roles that accessibility technologies support. For example, ROLE_SYSTEM_GROUPING / IA2_ROLE_SECTION / Group / ATK_ROLE_BLOCK_QUOTE / AXGroup. So I don't understand how it's possible to create custom widget names. Do these technologies have some sort of escape hatch?

> If control patterns are used does that mean that the browser may perform device independent actions on them? This would mean a JavaScript interface. 

By this do you mean things like https://github.com/a11y-api/a11y-api/'s [accessibility input events](https://a11y-api.github.io/a11y-api/spec/#accessibility-input-events-1)?

Not sure if I can help answer your latter two questions.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/553#issuecomment-241892869