Why this matters now: the 2025–2026 deadlines
If your typing test serves EU consumers (especially if you take payments, sell subscriptions, or run any e‑commerce flow), the European Accessibility Act (Directive (EU) 2019/882) applies from June 28, 2025. It covers selected products and services—including e‑commerce—and allows limited transitional arrangements until June 28, 2030 for services that rely on products already in lawful use before the applicability date. (eur-lex.europa.eu)
In the U.S., the Department of Justice finalized the ADA Title II web and mobile rule. State and local governments serving populations of 50,000+ must conform to WCAG 2.1 Level AA by April 24, 2026 (smaller entities by April 24, 2027). If your typing test powers public‑sector programs (schools, workforce agencies, libraries) or you contract with them, your product needs to meet these dates. (govinfo.gov)
Accessibility is also a market reality: about 1.3 billion people (16% of the world) live with significant disabilities, and more than 1 in 4 U.S. adults reported a disability in 2022. Building in accessible patterns helps them complete high‑focus tasks like timed typing tests. (who.int)
What auditors will look for (so you can build to pass)
- EN 301 549: This European standard is widely used for ICT conformance. For web content, Clause 9 maps directly to all WCAG 2.1 A and AA Success Criteria and the WCAG conformance requirements—if your web pages meet WCAG 2.1 AA, you satisfy Clause 9. (etsi.org)
- ADA Title II (U.S.): The final DOJ rule names WCAG 2.1 Level AA (2018 version) as the technical standard for covered web and mobile content, with the dates above. (govinfo.gov)
Translation: ship WCAG 2.1 AA. The checklist below focuses on the success criteria most likely to affect a typing‑test experience.
The prioritized checklist for typing‑test sites
Turn the mandates into UX wins by implementing these five items first.
1) Make the entire test operable with a keyboard
Typing tests are built for keyboards—make sure everything around the test is too.
- Ensure all functionality can be reached and executed via keyboard (SC 2.1.1), and that users can always move focus away—no keyboard traps (SC 2.1.2). Common pitfalls: custom modals that don’t return focus, off‑canvas menus that trap Tab, and “start test” buttons that only respond to clicks. (w3.org)
- Practical tips:
- Support Enter/Space for buttons and links built from custom elements.
- Trap focus inside open modals and restore it on close; Esc closes the dialog.
- Keep Tab order logical; avoid tabindex values > 0.
2) Always show a visible focus indicator
On timed tasks, users must see where they are. Provide a high‑contrast, consistent focus style (SC 2.4.7) and ensure it’s not “designed away” by CSS resets; also verify it meets Non‑Text Contrast (SC 1.4.11) where applicable. (w3.org)
Example CSS:
```css
:where(button, [role="button"], a, input, select, textarea):focus-visible {
outline: 3px solid #1e90ff;
outline-offset: 2px;
}
```
3) Time limits you can pause or extend (and warn before expiry)
WCAG’s Timing Adjustable (SC 2.2.1) lets people finish tasks under time pressure:
- Provide at least one of these: Turn off the time limit, let users adjust it, or offer an extension with a simple action; when you warn users, give them at least 20 seconds and allow extending at least 10 times.
- For typing tests, include Pause/Resume and “+30 seconds” (or similar) actions, and a setting to choose longer default durations before the test starts. (w3.org)
4) Announce timers and errors to assistive tech without hijacking focus
People using screen readers should hear important updates even if focus stays in the typing area.
- Status messages (SC 4.1.3): Announce non‑modal updates like “Timer paused,” “Time extended,” or “10 seconds remaining” using ARIA live regions (role="status" or aria-live="polite"). Avoid announcing every second—reserve announcements for meaningful thresholds. (w3.org)
- Error Identification (SC 3.3.1): When a user submits results or profile info with mistakes (e.g., missing name), present text errors near the fields and associate them via aria-describedby; if the error is global and urgent, use role="alert". (w3.org)
Example markup:
```html
Name
Enter your name before starting.
```
5) RTL and language support (for Arabic, Hebrew, and mixed‑language text)
Typing tests are global. Support right‑to‑left scripts and language changes so assistive tech reads correctly.
- Use the dir attribute ("rtl", "ltr", or "auto") and mirror UI affordances where appropriate; prefer semantic direction over only using CSS. (developer.mozilla.org)
- Mark passages with the correct lang and use Language of Parts (SC 3.1.2) where the UI or prompts switch language mid‑page. (w3.org)
Bonus: Respect users’ reduced‑motion preference
Some users experience dizziness or distraction from animation. Honor their OS setting with prefers-reduced-motion. While not a separate WCAG 2.1 AA criterion, it is a published W3C technique and a strong UX win, especially on ticking timers or celebratory confetti after a score. (w3.org)
Example CSS:
```css
@media (prefers-reduced-motion: reduce) {
.countdown { animation: none; transition: none; }
.confetti, .celebration { display: none; }
}
```
A practical 2025–2026 roadmap for teams
- This month
- Baseline audit against WCAG 2.1 AA for core flows: start test, typing area, pause/resume, results, sign‑in/checkout (if any), and settings.
- Fix keyboard traps and add visible focus styles site‑wide.
- Next 1–2 sprints
- Add time‑adjust/extend controls and a 20‑second warning before expiry.
- Implement live‑region announcements for pause/resume and final results; ensure form errors are programmatically associated.
- Quarter ahead
- Add RTL toggle tests and language‑of‑parts checks; document your conformance (accessibility statement) and how to request accommodations.
- Integrate reduced‑motion styles and test with OS settings.
Scope check and notes
- EU: The EAA applies to specific categories (including e‑commerce services). If your typing test includes purchasing or subscription flows for EU consumers, build to WCAG 2.1 AA and document EN 301 549 alignment. Transitional provisions let services keep using existing equipment until June 28, 2030, but new or substantially changed services from June 28, 2025 must comply. (eur-lex.europa.eu)
- U.S.: ADA Title II obligations fall on public entities; vendors providing their sites or apps to those entities should ship WCAG 2.1 AA now to meet April 24, 2026 (≥50,000 population) or April 24, 2027 (<50,000) deadlines. (govinfo.gov)
Bottom line
Build to WCAG 2.1 AA now—specifically: keyboard‑only operability, visible focus, time‑adjustable timers, and assistive‑tech‑friendly status/error messages, with RTL and reduced‑motion support. This hits EN 301 549 Clause 9 for the EU and the ADA Title II web rule in the U.S., and it makes your typing test faster, clearer, and fairer for everyone. (etsi.org)
