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
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?
The text was updated successfully, but these errors were encountered:
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.
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 theli
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?
The text was updated successfully, but these errors were encountered: