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

Organize Test Writing Priority by Feature Usage… #87

Open
cookiecrook opened this issue Dec 18, 2023 · 5 comments
Open

Organize Test Writing Priority by Feature Usage… #87

cookiecrook opened this issue Dec 18, 2023 · 5 comments
Labels

Comments

@cookiecrook
Copy link
Collaborator

cookiecrook commented Dec 18, 2023

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 test aria-hidden directly yet, we could probably write some tests that combine label or role computation with aria-hidden to find our where the most import aria-hidden-related interop challenges are.

Ditto for some other features.

@cookiecrook cookiecrook added blocked by testability desirable, but not testable yet and removed Agenda+ labels Jan 9, 2024
@cyns cyns self-assigned this Jan 9, 2024
@zcorpan
Copy link
Member

zcorpan commented Jan 9, 2024

We can also look at the State of HTML survey results for pain points with ARIA features.

@cookiecrook cookiecrook removed the blocked by testability desirable, but not testable yet label Jan 9, 2024
@cookiecrook
Copy link
Collaborator Author

ARIA features by page load usage in descending order from https://chromestatus.com/metrics/feature/popularity

ARIAHiddenAttribute (86%)
ARIALabelAttribute (67%)
ARIAExpandedAttribute (48%)
ARIALabelledByAttribute (43%)
ARIALiveAttribute (41%)
ARIAHasPopupAttribute (41%)
ARIAControlsAttribute (37%)
ARIADescribedByAttribute (27%)
ARIAAtomicAttribute (26%)

< 25%
ARIADisabledAttribute
ARIACheckedAttribute
ARIAAutocompleteAttribute
ARIAModalAttribute
ARIACurrentAttribute
ARIASelectedAttribute
ARIAValueTextAttribute
ARIAOwnsAttribute
ARIALevelAttribute
ARIAPressedAttribute
ARIAValueMinAttribute
ARIAValueMaxAttribute
ARIAValueNowAttribute
ARIAActiveDescendantAttribute
ARIARelevantAttribute
ARIABusyAttribute

< 5%
ARIAKeyShortcutsAttribute 
ARIAInvalidAttribute
ARIAGrabbedAttribute (deprecated)
ARIARequiredAttribute
ARIAPosInSetAttribute
ARIASetSizeAttribute
ARIAOrientationAttribute
ARIARoleDescriptionAttribute
ARIAReadOnlyAttribute
ARIAMultiselectableAttribute
ARIAMultilineAttribute
ARIADescriptionAttribute
ARIASortAttribute

< 1%
ARIARowCountAttribute
ARIAColIndexAttribute
ARIARowIndexAttribute
ARIADetailsAttribute
ARIAColCountAttribute
ARIAErrorMessageAttribute
ARIAPlaceholderAttribute
ARIADropEffectAttribute (deprecated)

< 0.1%
ARIALabeledByAttribute (non-standard spelling 0.0971%)
ARIAFlowToAttribute
ARIAColSpanAttribute
ARIARowSpanAttribute
ARIAAnnotations
ARIAVirtualcontentAttribute (proposed attr, never standardized)

@cookiecrook
Copy link
Collaborator Author

cookiecrook commented Jan 10, 2024

Even though we can't test aria-hidden directly yet, we could probably write some tests that combine label or role computation with aria-hidden to find our where the most import aria-hidden-related interop challenges are.

Filing this as a standalone issue since it's the only part of this that is not blocked by missing WebDriver features.

@cookiecrook
Copy link
Collaborator Author

cookiecrook commented Feb 6, 2024

Even though this is blocked, I'm hoping it will be unblocked later this year, so adding the 2024-investigation label.

@cookiecrook
Copy link
Collaborator Author

#92 and #93 are prime candidates.

@cookiecrook cookiecrook changed the title Organize 2024 Investigation Test Writing Priority by Feature Usage… Organize Test Writing Priority by Feature Usage… Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants