Add a page about accessibility standards we support
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 11
- Forks
- 22
- Avg merge
- 7d 3h
- Merged PRs (30d)
- 2
Description
Accessibility section should have a page that outlines the standards we support.
Added in 2.0:
- Full Keyboard Support (WCAG 2.0, 2.1.1, Level A, Keyboard; WCAG 2.0, 2.1.2, Level A, No Keyboard Trap)
- Consistent Navigation (WCAG 2.0, 3.2.3, Level AA, Consistent Navigation)
- Tabbing/Reading Order (WCAG 2.0, 2.4.3, Level A, Focus Order)
- Focus Visible (WCAG 2.0, 2.4.7, Level AA, Focus Visible)
- Grouping
(ask Miguel for the grouping one)
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 locating the repository's accessibility section and review how documentation pages are structured. Create a page covering the listed WCAG standards, and confirm the missing Grouping standard with Miguel before considering the page complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100