web-platform-tests
Consider adding Acacia AAM testing to the 2024 Investigation
Should we bring in @spectranaut and @alice's work on the Acacia AAM testing in the scoring criteria for the 2024 Accessibility Investigation? They made significant progress recently and including it would bring the RFC more visibility.
Originally posted by @cookiecrook in https://github.com/web-platform-tests/interop-accessibility/issues/90#issuecomment-2287320893
For context, the webdriver extensions (item one of the investigation list) went from 25% to 50% when we abandoned the tree dump approach. So some or all of that 25% could be reapplied to the Acacia effort given how much progress has been made in the last several months.
Discussing some with @spectranaut offline... What about these?
- 25% Acacia AAM test exploration
- 5% initial prototype (complete)
- 5% functional in x,y,z implementations/APIs (some complete)
- 5% RFC consensus?
- 5% functional in WPT CI?
- 5% additional test writing?