Interop 2025 Accessibility Investigation

[zcorpan]

FYI, I've filed web-platform-tests/interop#866 to continue this investigation effort for next year.

Prior years' investigations:

• Scoring criteria for Interop 2023 Accessibility Testing Investigation #3
• Interop 2024 Accessibility Investigation #90

Next year's carry-on investigation:

• Interop 2026 Accessibility Investigation #202

2025 Accessibility Investigation

• (35%) Accessible Node or similar API

  • (10%) Initial spec language agreement of Accessible Node (DRI @cookiecrook)
    • Computing the Accessible Backing Node, or a similar test-only interface WICG/aom#197 and/or
    • Explainer: WebDriver Extension for Accessible Nodes, etc. (potential solution for #197) WICG/aom#203
    • 5% RFC proposal Tentative testdriver methods rfcs#226
    • 5% RFC agreement (Review wpt RFC about tentative testdriver methods (for AccessibleNode) #191) and spec language
  • (15%) Initial implementation of Accessible Node (behind runtime flag?) in WebKit, Chromium, Gecko
    • (5%) First Implementation in Gecko #1929144 @jcsteh
    • (5%) Second Implementation in WebKit #299508 @rahimabdi
    • (5%) Third Implementation
  • (10%) Tree Walker investigation using Accessible Node
    • (6%) Write basic tree walker tests (tentative) that purposefully avoid all known tree implementation differences (scroll areas, pseudo elements and other generated content, etc.)
    • (4%) Author investigation tests for which parts of Node or Tree might be standardized in 2025 or later?
      • (2%) Purposefully write failing tests (tentative) that expose the areas where the internal accessibility tree differ between engines
      • (2%) File AOM or ARIA issues if it appears are some tree relationships that might be standardized as part of a 2025 Investigation

• (35%) Acacia AAM test exploration (DRI @spectranaut)

  • (10%) functional in implementations/APIs
    • not calling out all combos, but as examples:
      • Mac AX API in WebKit, Chromium, Gecko
      • Linux GTK in Chromium, Gecko
      • Windows UIA in Chromium, Gecko
      • Others?
        • Window MSAA? in Chromium, Gecko
        • Window IA2? in Chromium, Gecko
  • (10%) RFC consensus?
  • (10%) functional in WPT CI?
    • Everyone please review Extend testdriver.js and wptrunner to test AAMs (platform accessibility APIs) wpt#53733
  • (5%) additional test writing?

• (30%) Miscellaneous

  • Review and possibly port Chromium accname tests into WPT #41 (@jnurthen)
  • add error handling for missing attrs in aria-utils.js #74 (@janewman)
  • Add SVG name fallback tests from aria attrs to host lang title etc #84 (@adampage?)
  • Tests for removal of aria-hidden=false #88 (@rahimabdi)
  • Test aria-hidden using label/role where possible #91
  • Investigate keyboard operability testing #101 (@rahimabdi)

More issues from:

• 2025-investigation-candidate

[cookiecrook]

I fixed the percentages to realign with 100% after replanning changes. Open to adjustment of course, but at least the math should be right. Current progress at 30%. PR: web-platform-tests/wpt.fyi#4492