Accessibility: 9 links without accessible text on react.dev (WCAG 2.4.4)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Summary
An automated WCAG accessibility scan of react.dev found 3 issues affecting ADA compliance:
Score: 20/100 (Grade F) — CRITICAL risk tier
Issues Found
| # | Severity | Issue | WCAG |
|---|---|---|---|
| 1 | CRITICAL | 9 links without accessible text | 2.4.4 Link Purpose (Level A) |
| 2 | SERIOUS | Missing skip navigation link | 2.4.1 Bypass Blocks (Level A) |
| 3 | MODERATE | Heading hierarchy skips (h2 → h4) | 1.3.1 Info and Relationships (Level A) |
Suggested Fixes
1. Links without accessible text (CRITICAL)
9 links have no visible text, aria-label, or image alt text. Screen readers announce these as "link" with no purpose.
<!-- Before -->
<a href="/learn"><svg>...</svg></a>
<!-- After -->
<a href="/learn" aria-label="Learn React"><svg>...</svg></a>
2. Missing skip navigation (SERIOUS)
No skip-to-content link found. Keyboard-only users must tab through the entire sidebar and nav on every page load.
<body>
<a href="#main" class="sr-only focus:not-sr-only focus:absolute focus:z-50 focus:p-4">
Skip to main content
</a>
...
<main id="main">...</main>
</body>
3. Heading hierarchy (MODERATE)
Heading levels skip from h2 to h4, which confuses screen reader users navigating by heading.
Why This Matters
- React is used by millions of developers who look to react.dev as an example
- WCAG 2.4.4 (Link Purpose) is among the most cited ADA violations
- Leading by example on accessibility helps the entire React ecosystem
Reproduction
npx accessscore https://react.dev
Scanned with AccessScore — open source WCAG/ADA checker.
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 running the reported npx accessscore https://react.dev scan and reviewing the react.dev navigation, links, and heading structure it identifies. Address the nine textless links, add skip navigation, and correct the reported heading hierarchy; done means the scan findings are resolved and the site remains keyboard and screen-reader navigable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- accessibility, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100