Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding Acacia AAM testing to the 2024 Investigation #139

Closed
cookiecrook opened this issue Aug 14, 2024 · 3 comments
Closed

Consider adding Acacia AAM testing to the 2024 Investigation #139

cookiecrook opened this issue Aug 14, 2024 · 3 comments

Comments

@cookiecrook
Copy link
Collaborator

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 #90 (comment)

@cookiecrook
Copy link
Collaborator Author

cookiecrook commented Aug 14, 2024

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.

@cookiecrook
Copy link
Collaborator Author

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?

@cookiecrook
Copy link
Collaborator Author

Resolved in #140. Scoring criteria updated. Closing as task complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant