1929144 - Make it possible to test additional accessibility properties in WPT

Status: ASSIGNED

(Core :: Disability Access APIs, task)

Description

[James Teh [:Jamie]]

It's currently possible to test computed accessibility labels and roles in WPT. We want to be able to test other properties, including description, states (checked/pressed/selected/etc.), tree relationships (parent/children), etc. This is being discussed between browser vendors and others in a few places, in order of specificity:
https://github.com/WICG/aom/issues/203
https://github.com/WICG/aom/issues/197
https://github.com/web-platform-tests/interop-accessibility/issues/90

I'm starting to prototype this in Gecko. Initially, this bug will be used to track work in progress, but it may be repurposed or split up as the work gets further along.

Comment 1

[James Teh [:Jamie]]

Attachment: Bug 1929144 part 1: Implement accessibleNode in marionette.

Comment 2

[James Teh [:Jamie]]

Attachment: Bug 1929144 part 5 WIP: Add simple WPT tests exercising AccessibleNode.

Comment 3

[James Teh [:Jamie]]

Attachment: Bug 1929144 part 3 WIP: Implement generation of ids for accessibleNode, as well as exposure of parent and children.

Comment 4

[James Teh [:Jamie]]

Attachment: Bug 1929144 part 3: Implement AccessibleNode in WPT.

Comment 5

[James Teh [:Jamie]]

Attachment: Bug 1929144 part 5 WIP: Add a basic WPT test for the accessibility tree.

Comment 6

[James Teh [:Jamie]]

Attachment: Bug 1929144 part 4 WIP: Add AriaUtils.verifyAccessibilityTree for simpler tree verification using a simple JS object.

Comment 7

[James Teh [:Jamie]]

Hey :jgraham. This is still WIP, but I'd be grateful for some guidance on where to go from here. This "works", but there are obviously design/API shape questions that need to be answered and addressed. I'm somewhat blocked until I can get answers to those. See the questions in D227917. Thanks.

Comment 8

[James Graham [:jgraham]]

I've added some comments in the review. Sorry for the long delay.

Comment 9

[James Teh [:Jamie]]

Attachment: Bug 1929144 part 2: Implement AccessibleNode in marionette_driver.

Because there is no DOM object for accessible nodes, Marionette:GetAccessibleNode is exposed as a simple method on the Marionette class, taking the id of the requested node as an argument.