Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552)

> If having a complete ARIA implementation of HTML roles would be useful, and assuming ARIA WG agrees to doing the work, would a logical next step be to bring people together to complete the HTML as Custom Elements as a reference?

It might be an interesting project, but it's a large one, and there are several other blockers to getting full parity (see https://github.com/domenic/html-as-custom-elements/issues/27 and other issues under https://github.com/domenic/html-as-custom-elements/issues?q=is%3Aissue+is%3Aopen+label%3Aprimitive for just the things I discovered while working on a very small set of elements; others are summarized on https://domenic.github.io/html-as-custom-elements/, and https://github.com/domenic/html-as-custom-elements/blob/master/docs/accessibility.md points out that we also need states and properties, not just roles).

I'm not sure by what criteria it would be the next logical step---what are we stepping toward?

-- 
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/552#issuecomment-242153166