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
The new HTML customized select can have have buttons and links inside of options, and the plan is to both allow tab navigation to them, as well as to expose via the actions interface, as if aria-actions was used.
Question: how about we do this for any option, even an ARIA option? After all, it shouldn't care whether the button or link inside is from HTML or ARIA. I think it would be more consistent, and improve the a11y of existing content. I don't imagine scenarios where it would make things worse.
The text was updated successfully, but these errors were encountered:
The new HTML customized select can have have buttons and links inside of options, and the plan is to both allow tab navigation to them, as well as to expose via the actions interface, as if aria-actions was used.
Question: how about we do this for any option, even an ARIA option? After all, it shouldn't care whether the button or link inside is from HTML or ARIA. I think it would be more consistent, and improve the a11y of existing content. I don't imagine scenarios where it would make things worse.
The text was updated successfully, but these errors were encountered: