-
Notifications
You must be signed in to change notification settings - Fork 5
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
Organize Test Writing Priority by Feature Usage… #87
Comments
We can also look at the State of HTML survey results for pain points with ARIA features.
|
ARIA features by page load usage in descending order from https://chromestatus.com/metrics/feature/popularity
|
Filing this as a standalone issue since it's the only part of this that is not blocked by missing WebDriver features. |
Even though this is blocked, I'm hoping it will be unblocked later this year, so adding the 2024-investigation label. |
Organize 2024 Investigation Test Writing Priority by Feature Usage…
In addition to some of the new WebDriver or testability explorations, we should investigate future accessibility test writing priority by most used features.
For example, Chrome Feature Status logging seems to indicate
aria-hidden
is the most used ARIA feature, included on ~86% of page loads. Even though we can't testaria-hidden
directly yet, we could probably write some tests that combine label or role computation witharia-hidden
to find our where the most importaria-hidden
-related interop challenges are.Ditto for some other features.
The text was updated successfully, but these errors were encountered: