-
Notifications
You must be signed in to change notification settings - Fork 126
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
[Question] wai-aria/role/listbox-roles.html wpt test #2012
Comments
As a summary for the ARIA WG members, various WPT tests ensure that "orphaned" roles—that is, roles that are used outside a required context—are invalidated by the engine... Examples include an orphaned <div role="gridcell">Not a gridcell, because there is no row or grid context.</div> The ARIA section on Required Accessibility Parent Role (formerly "scope" or "required context role") mentions a few requirements for authors (ensure the correct context) and user agents (ignore generics in between). However, if I'm understanding @hs85jeong's issue correctly, they are concerned that there is not a requirement such as:
I am hopeful they agree with my summary above, and can clarify whether their opinion of the issue at hand is:
I'm not sure which @hs85jeong is suggesting as the solution, and I don't want to assume. |
My question is closer to 2. |
There is nothing precluding the User Agent from doing this, like a "User Agent SHOULD NOT or MUST NOT" statement, so I am confident it is acceptable to proceed with the Chromium patch. That said, I think it's worth the ARIA Working Group considering whether to add:
|
Aren't the WPT tests only going to fail on MUSTs? |
okay then, Working Group SHOULD consider MUST… 😉 |
note for self: |
The WPT contextual role invalidation tests may be helpful here: web-platform-tests/interop-accessibility#20. @scottaohara In addition to guidance on UA behavior for contextual roles, I'm curious if there's any crossover with this issue and the proposed role calculation algorithm: #2064. |
Hello @cookiecrook and @howard-e
I'm preparing a commit to fix the test that is failing on chromium.
If you can check the ARIA Spec, there is no text related to the User Agent regarding the case where the option is orphaned.
Could you check the reason why this test was added and where it is specified?
I can apply the changes only when this is confirmed.
Thank you.
The text was updated successfully, but these errors were encountered: