AccessKit / AccessKit/accesskit
Possible bug with `Node::set_expanded`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 114
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 28
Description
I'm trying to add the expanded property to a button. However, after doing so, using accessibility insights on Windows, I don't get the expected ExpandCollapsePattern and in fact I lose the InvokePattern that was working before I added the expanded property. I also tried adding expand and collapse actions but this seemed to make no difference. It's quite possible that this isn't a bug and just user error, but if so I would appreciate some pointers in the right direction as I'm quite stuck.
For context I'm trying to create an accordion widget and the ARAI pattern suggests adding the expanded property to the button: https://www.w3.org/WAI/ARIA/apg/patterns/accordion/
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 reproducing Node::set_expanded with the accordion button on Windows and inspect the resulting patterns in Accessibility Insights. Compare behavior before and after setting the expanded property, including any expand and collapse actions; done means the cause is identified and the expected ExpandCollapsePattern and InvokePattern behavior is restored or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100