AccessKit / AccessKit/accesskit
Design events
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 114
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 28
Description
Accessibility APIs require applications to raise events when the UI state changes, or in some cases, when UI elements are added or removed. AccessKit should imply as many of these events as possible from tree updates, to make it as easy as possible to implement accessibility correctly and completely. But some events will need to be raised directly by toolkits.
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
The issue names no files, tests, or entry points. Start by locating how tree updates and accessibility events are represented in AccessKit, then determine which events can be inferred and which toolkits must raise directly. Done requires an agreed design for covering UI state changes and element additions or removals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100