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

1. 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? 
2. If control patterns are used does that mean that the browser may perform device independent actions on them? This would mean a JavaScript interface. 
3. If such patterns were created with the browser manufacturers agree to expose them through standard interfaces on the platform so that assistive technology could interact with them?
4. Would there be a preferred other mechanism for extensibility?

-- 
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