You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We also should be able to get pretty granular about the per-file subsections of spec testing, for example... We could associate a specific label with the invalid roles related tests, or some subsection of the AccName name computation algorithm.
So the ARIA WG should consider what labels they want to sub-filter WPT test results...
@jnurthen had mentioned this could be useful like a "Can-I-Use" live link from the spec to its implementation status in all engines.
The text was updated successfully, but these errors were encountered:
You can only label a directory (including all its files) or you can label a file (including all its subtests). If the ARIA WG wants a higher level of granularity, it could file a new issue to the wpt.fyi repo, or consider splitting up some of the existing test files.
Now that the following issue and PR have landed:
My goal with:
Was to get the following links (and others as needed)
General label:
Accessibility: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=label%3Aaccessibility (or a11y synonym)
Or more specifically by spec:
ARIA: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=label%3Aaria
AccName: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=label%3Aaccname
HTML-AAM: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=label%3Ahtml-aam
We also should be able to get pretty granular about the per-file subsections of spec testing, for example... We could associate a specific label with the invalid roles related tests, or some subsection of the AccName name computation algorithm.
So the ARIA WG should consider what labels they want to sub-filter WPT test results...
@jnurthen had mentioned this could be useful like a "Can-I-Use" live link from the spec to its implementation status in all engines.
The text was updated successfully, but these errors were encountered: