AccessKit / AccessKit/accesskit
How does the Owns property work?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 114
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 28
Description
I notice that AccessKit includes the concept of a node owning another node, but this doesn't seem to be implemented anywhere?
I'm interested in what the design for this is envisaged to be? If I set Node A to own Node C, but Node B marks it C as a child, will AccessKit handle this "properly"?
I would assume accesskit could gracefully handle this such that ATs see Node C as a child of A NOT B? Is this desirable?
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 examining how AccessKit represents node ownership and child relationships, then compare the Node A/Node B/Node C scenario described here. Determine the intended behavior for assistive technologies when ownership conflicts with parentage, and document the design decision or implementation scope before coding.
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