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

@domenic "I'm not sure exactly what this means. The HTML as Custom Elements project was where I first encountered the problem, where if I wanted to do something
very simple like create a  <custom-p> , there was no way to get accessibility tech to treat my element as a paragraph (i.e. no way to get  IA2_ROLE_PARAGRAPH 
/  ATK_ROLE_PARAGRAPH ). It certainly makes it clear that without these additional roles, custom elements cannot be said to "explain the platform", because
the platform has the ability to tell AT that a given element is a paragraph, whereas author code does not."

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?

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