[openable] do we need exclusive openables?
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Details elements can be linked together to create an exclusive accordion pattern (this is contentious and should probably have an opt-out in browser settings).
We should decide if and how this pattern can be applied to openables. For tab like UI this would be nice to have without JS though you would still need JS for an accessible tab component (for now).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's discussion of Details elements, openables, and exclusive accordion behavior. Determine whether an exclusive pattern should be supported, how it would apply to tab-like UI, and whether an opt-out is needed in browser settings. Done means the proposal has a decided scope and documented behavior, including the relationship to accessible tab components and JavaScript.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- accessibility, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100