Skip to content

Body element likely should not map to ARIA document role #117

Closed

Description

@joanmarie

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

  1. self-assigned this
    on Jan 30, 2018
  2. jasonkiss commented on Feb 6, 2018

    @jasonkiss
    Contributor

    Thanks @joanmarie.

    I've updated all mappings for body based on your summary and how the other browsers are currently mapping it. See 724677b.

    Please reopen if something's not right.

  3. joanmarie commented on Feb 6, 2018

    @joanmarie
    ContributorAuthor

    Everything other than UIA looks right to me. Since I know nothing about UIA other than what @boggydigital tells me, we should ask him. 😄

  4. jasonkiss commented on Feb 6, 2018

    @jasonkiss
    Contributor

    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.

  5. boggydigital commented on Mar 2, 2018

    @boggydigital
    Contributor

    Verified that UIA mapping is correct, closing the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions