You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Body element likely should not map to ARIA document role #117
The HTML AAM currently maps body to the ARIA document role. But some accessibility APIs expect different mappings. For instance, in macOS the accessible object corresponding to body has a role of AXWebArea but the ARIA document role is an AXGroup (with a subrole of AXDocument). Similarly, in ATK, the accessible object corresponding to body should[*] be exposed as ATK_ROLE_DOCUMENT_WEB, with ATK_ROLE_DOCUMENT_FRAME being used for the document role.
[*] Gecko currently fails to do this, but I plan to provide a patch to fix that. WebKitGtk does it correctly.
Activity
update <body> mappings / issue #117
jasonkiss commentedon Feb 6, 2018
Thanks @joanmarie.
I've updated all mappings for
bodybased on your summary and how the other browsers are currently mapping it. See 724677b.Please reopen if something's not right.
joanmarie commentedon Feb 6, 2018
Everything other than UIA looks right to me. Since I know nothing about UIA other than what @boggydigital tells me, we should ask him. 😄
jasonkiss commentedon Feb 6, 2018
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.
boggydigital commentedon Mar 2, 2018
Verified that UIA mapping is correct, closing the issue