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

Tri-State Checkbox Example: clarify usage of aria-controls #1352

Closed
jscholes opened this issue Nov 5, 2020 · 1 comment
Closed

Tri-State Checkbox Example: clarify usage of aria-controls #1352

jscholes opened this issue Nov 5, 2020 · 1 comment

Comments

@jscholes
Copy link

jscholes commented Nov 5, 2020

In the Tri-State Checkbox Example, aria-controls is applied to the "All condiments" checkbox, with a value referencing all four IDs of the individual condiment two-state checkboxes. This is programmatically correct, but:

  • aria-controls usage isn't mentioned anywhere within the Checkbox design pattern; and
  • as covered in What to do about aria-controls #995, there is still no consensus about how aria-controls should be surfaced by assistive technology. Indeed, the previous surfacing by JAWS (now silenced by default) didn't take multiple IDREFs into account.

Given the above, should aria-controls usage be added to the "WAI-ARIA Roles, States, and Properties" section of the Checkbox design pattern? And for the purposes of ARIA-AT testing (ref: w3c/aria-at#322), my belief is that no assertions can be included as of the time of filing, because there is no meaningful understanding of how to surface the information.

@jscholes
Copy link
Author

jscholes commented Nov 5, 2020

Accidentally filed here due to browser autocomplete mistake. Apologies; actual issue is: w3c/aria-practices#1599

@jscholes jscholes closed this as completed Nov 5, 2020
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