-
Notifications
You must be signed in to change notification settings - Fork 125
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
Element.prototype.role #1612
Comments
@jonathantneal does https://wicg.github.io/aom/explainer.html#what-happened-to-accessiblenode help explain why this doesn't work today? ARIA 1.2 only defines reflection of explicitly defined ARIA roles - it does not imply that implicit roles are exposed and indeed this is unlikely at this point in time. It sounds like you want https://wicg.github.io/aom/explainer.html#full-introspection-of-an-accessibility-tree---computedaccessiblenode which IMO is unlikely to ever be implemented outside of testing/developer tooling. |
The rationale in that document seems specific to one particular implementation that never shipped. Based on what ships in Safari, I would have expected I’m pretty unsure where my issue belongs. Still, Perhaps I can better organize my questions:
|
@jonathantneal computedRole is being discussed as part of both WebDriver and AOM, but what you're requesting has some implementation blockers at the moment. In particular, role heuristics are usually only computed if AT needs it. Allowing web authors to trigger this on demand (by checking the computed role) has performance implications. Closing, but reopen if you think this is worth continuing discuss within ARIA. |
I’ve noticed that
Element.prototype.role
has an incomplete implementation in Safari.I would have expected this reflection:
Is there documentation or a proposal for this behavior specified somewhere?
Would this be part of ARIA, AOM, or something else?
The text was updated successfully, but these errors were encountered: