-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help locating some features of the accessibility mapping #90
Comments
I'm not completely sure if this answers your question, but HTML-AAM section 4.3 Exposing HTML Features That Do Not Directly Map to Accessibility APIs might be what you are looking for. It says:
There are examples of this (I think?) in 4.3.1:
The current ARIA 1.2 role parity work may reduce the need for some of those. So, I have a question. Why would a custom element author assign a default role instead of just setting the role? For example, a |
Hmm, this doesn't seem to help that much, sadly. For example, I'm looking for what text normatively requires that
Let's open a separate issue to discuss this, so this one can stay focused on finding out how UAs are required to implement accessibility mappings. |
@domenic |
Thank you! I think you are referring to this text:
This seems to fit, if I am correct that:
I think that answers the question, and also gives the right extensibility point: for custom elements, HTML needs to define that it's no longer just the |
@joanmarie this was not as easy to find as I would have liked (also hidden in a block with a non-obvious heading). I think this might be a candidate for an editorial re-write. |
Moving to 1.3 - this will not make 1.2 |
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:
role=""
attribute is set, use that, then map to native platforms using https://w3c.github.io/core-aam/.(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:
role=""
attribute is set, use that, then map to native platforms using https://w3c.github.io/core-aam/.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!
The text was updated successfully, but these errors were encountered: