When to automatically expose actions on an option (ARIA only or HTML options too?)

Question

When to automatically expose actions on an option (ARIA only or HTML options too?)

aleventhal opened this issue 2 months ago · 7 comments

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.

Answer 1 · 2024-09-25T20:59:02.000Z

@smhigley @jcsteh @scottaohara

Answer 2 · 2024-09-26T09:09:13.000Z

@aleventhal If it works in HTML, ARIA should also allow it. But I am not aware that this is possible with HTML. Where is this specified?

Answer 3 · 2024-09-26T09:18:09.000Z

@JAWS-test this refers to a new proposal: https://developer.chrome.com/blog/rfc-customizable-select

Answer 4 · 2024-09-26T09:55:04.000Z

@pkra https://developer.chrome.com/blog/rfc-customizable-select:

you can add arbitrary non-interactive content within the option elements

I did not find on the page you mentioned that option elements may contain links and buttons. On the contrary, it says that this remains prohibited. Therefore the suggestion of @aleventhal refers to another page or the suggestion does not seem to be correct