-
Notifications
You must be signed in to change notification settings - Fork 27
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
Body element likely should not map to ARIA document role #117
Comments
Thanks @joanmarie. I've updated all mappings for Please reopen if something's not right. |
Everything other than UIA looks right to me. Since I know nothing about UIA other than what @boggydigital tells me, we should ask him. 😄 |
Control Type Pane is what Inspect.exe tells me, but I could be reading it wrong. Reopening for @boggydigital to confirm and close or advise otherwise. |
Verified that UIA mapping is correct, closing the issue |
The HTML AAM currently maps
body
to the ARIAdocument
role. But some accessibility APIs expect different mappings. For instance, in macOS the accessible object corresponding tobody
has a role of AXWebArea but the ARIAdocument
role is an AXGroup (with a subrole of AXDocument). Similarly, in ATK, the accessible object corresponding tobody
should[*] be exposed as ATK_ROLE_DOCUMENT_WEB, with ATK_ROLE_DOCUMENT_FRAME being used for thedocument
role.[*] Gecko currently fails to do this, but I plan to provide a patch to fix that. WebKitGtk does it correctly.
The text was updated successfully, but these errors were encountered: