Interop 2025 Accessibility Investigation

[zcorpan]

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

Roadmap should be filled in after this year's investigation:

• Interop 2024 Accessibility Investigation #90

TBD re-evaluate percentages.

• (25%) 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
  • (10%) Initial implementation of Accessible Node (behind runtime flag?) in WebKit, Chromium, Gecko
    • (5%) First Implementation in Gecko #1929144
    • (3%) Second Implementation
    • (2%) Third Implementation
  • (5%) Tree Walker investigation using Accessible Node
    • (3%) Write basic tree walker tests (tentative) that purposefully avoid all known tree implementation differences (scroll areas, pseudo elements and other generated content, etc.)
    • (2%) Author investigation tests for which parts of Node or Tree might be standardized in 2025 or later?
      • (1%) Purposefully write failing tests (tentative) that expose the areas where the internal accessibility tree differ between engines
      • (1%) File AOM or ARIA issues if it appears are some tree relationships that might be standardized as part of a 2025 Investigation

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

  • (5%) 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
  • (5%) RFC consensus?
  • (5%) functional in WPT CI?
  • (5%) additional test writing?

• (20%) 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
  • Tests for removal of aria-hidden=false #88 (@rahimabdi)
  • Test aria-hidden using label/role where possible #91
  • Investigate keyboard operability testing #101 (@rahimabdi)

Possibly more issues:

• 2025-investigation-candidate
• Triaging in reverse chronology.... through Revisit display: contents accessibility once more thorough API is available #97 during Jan 7th meeting