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

> What new roles do we specifically need?

There are a bunch of them. If you go to https://w3c.github.io/aria/html-aam/html-aam.html#html-element-role-mappings, click "View as a single table", there are a bunch of rows with "No corresponding role". Here are the first few interesting ones (i.e. ones that seem to have interesting native correspondences with AT, as shown by the subsequent columns):

- audio
- blockquote
- br ("whitespace" role)
- canvas
- caption
- details

> do you see the work you began in HTML as Custom Elements as a logical extension to this? 

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.

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