Accessibility improvement
Open
Nobody has claimed this yet.
improvement
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
There are several accessibility issues on the interface by the WCAG standard (https://www.w3.org/WAI/standards-guidelines/wcag/)
- no skip link, no level one heading (https://www.w3.org/TR/WCAG21/#bypass-blocks)
- focus is not visible (https://www.w3.org/TR/WCAG21/#focus-visible)
- lack of proper landmarks (https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA11)
Describe the solution you'd like
- improve landmarks
- add skip link and level one heading
- improve focus styling
I'm happy to send pull request to fix step by step.
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 specific entry points. Start by locating the interface's main layout and page structure, then compare it with the linked WCAG guidance; done means the requested landmarks, skip link, level-one heading, and visible focus styling are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100