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

binary self-toggle switches #20

Open
scottaohara opened this issue May 7, 2022 · 1 comment
Open

binary self-toggle switches #20

scottaohara opened this issue May 7, 2022 · 1 comment
Labels
a11y accessibility issues

Comments

@scottaohara
Copy link

since this is constructed with a ul element as its base, it seems like the intent here was to create a list of items. However, because the li elements are having their role overwritten by ARIA, the list semantics are completely lost here resulting in a bunch of sibling buttons.

Is there a way to declare if one wanted these to behave (be exposed as) as checkboxes, toggle buttons or switches?

@jerivas
Copy link
Member

jerivas commented May 12, 2022

Scott, I've been following your work for years and appreciate your input on these issues!

I wonder if the solution is to discourage authors from using toggle-trigger on non-interactive elements. For this example it would mean nesting actual buttons in the lis.

We could also propose new element (<toggle>?) that browsers can enforce the correct semantics on, kinda like <summary>. No idea what that means for the spec though.

@mirisuzanne mirisuzanne added the a11y accessibility issues label May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y accessibility issues
Projects
None yet
Development

No branches or pull requests

3 participants