Accessibility Tree details
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 8
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I am unsure about a sentence in the document, so making an issue to inquire further:
In general, the accessibility tree is a simplified version of the DOM in that only information needed by AT is exposed. For example, a span with no semantic information will not be part of the accessibility tree.
I made a document containing two unmarked spans, and am seeing both Firefox and Chrome include them in the AT tree. See screenshot at the bottom.
I also enabled chrome's Screen Reader (which is the only app i have succeeded with using on linux) and it spoke both spans by default.
So what exactly does "not be part of" mean in the sentence?
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 with the quoted sentence about accessibility trees in the document and review the reported Firefox and Chrome behavior, including the linked screenshot. Check what “not be part of” is intended to mean, then clarify the sentence so its treatment of unmarked spans is unambiguous. Done means the documentation accurately explains the observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100