Uh oh!
There was an error while loading. Please reload this page.
ActionList: Correct semantics for Groups - #1598
Conversation
🦋 Changeset detectedLatest commit: 40481f3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
| /** | ||
| * The ARIA role describing the function of the list inside `Group` component. `listbox` or `menu` are a common values. | ||
| */ | ||
| role?: AriaRole |
There was a problem hiding this comment.
Question: Given there's a limited number of suitable roles for this component, can we help the user decision along by providing a union of those compatible types?
There was a problem hiding this comment.
I'm a bit hesitant because it's heavily context dependent so it's hard to create good types for it.
- I'm hoping to set these automatically when you use our menu components like ActionMenu or SelectPanel and increase their coverage.
- For building your menu story (common escape hatch in memex), I'm a bit hesitant about adding "hints" that send you the wrong way - classic a11y story, better to not say anything than say the wrong thing
I think I'll come around to this feeling more confident when we replace the escape hatches in memex with the right menu components (ActionMenu/Autocomplete/SelectPanel/etc)
checklist:
ulinside aliul.Headeris for visual users only. It's hidden for screen readers.roleThis is the generated HTML, formatted for legibility:
Merge checklist