Help locating some features of the accessibility mapping · Issue #90 · w3c/core-aam (original) (raw)

Hi all,

I'm working with @alice and @tkent-google on allowing custom elements to specify their own default roles/states/properties. We think we have a rough plan, but need help in one regard. I will use role as the example, but the same reasoning should hold for states/properties, I think.

Right now, to our understanding, implementation behavior for an element's role is:

1. If the role="" attribute is set, use that, then map to native platforms using https://w3c.github.io/core-aam/.
2. Otherwise, map to native platforms using https://w3c.github.io/html-aam/#html-element-role-mappings

(side note: I can't find how to apply step 2 for custom elements; that is, I wasn't able to find a part of HTML-AAM that states how unknown tags map.)

We want to modify this to be something like:

1. If the role="" attribute is set, use that, then map to native platforms using https://w3c.github.io/core-aam/.
2. If the element is a custom element, and the custom element author has set a default ARIA role, then use that, mapping to native platforms using core-aam.
3. Otherwise, map to native platforms using https://w3c.github.io/html-aam/#html-element-role-mappings

However, I can't find where this 2-step algorithm might be defined today in specifications, so that we can properly insert this new step in the middle. Could folks help use locate that?

Thanks!