Carryover evaluation: Accessibility Testing Investigation

[zcorpan]

Description

Carry-over investigation of the accessibility investigation. Previous proposal: #866

Rationale

Browsers should investigate and work towards generating consistent accessibility trees from the same DOM + CSS. Additional investigation and testing infrastructure for accessibility testing is still needed.

Investigation Roadmap

Continue to make progress on the items in web-platform-tests/interop-accessibility#148 so that more of the accessibility stack is testable in wpt. Any new scope TBD.

[zcorpan]

To be considered for scope inclusion: #1065

[cookiecrook]

Discussed and supported in Accessibility Interop meeting October 7th, 2025.

There is significant recent progress in this area.

• WebDriver/AOM extensions nearing two implementations of tentative ~"get accessibility properties"
  • Gecko
  • WebKit
• Acacia AAM Testing: Extend testdriver.js and wptrunner to test AAMs (platform accessibility APIs) wpt#53733
• WPT RFC: Tentative testdriver methods rfcs#226

Once landed, these should provide a framework for a significant amount of new accessibility tests in WPT, which we may complete during the Interop 2026 Investigation timeline, leading to the potential for another Accessibility Focus Area in Interop 2027.