AccessibleDOMNode : AccessibleNode is confusing
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 603
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Can we please nave these things differently? It's quite confusing, particularly as all DOM nodes are by definition accessible.
Contributor guide
No contributing guide indexed for this repository
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 AccessibleDOMNode and AccessibleNode but provides no files, tests, entry points, or replacement terminology. First trace where these AOM terms are defined and referenced, then confirm the intended names and update scope before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100