React WCAG 2.1 Checker

WCAG 2.1 for React Sites

WCAG 2.1 became a W3C Recommendation in June 2018. It added criteria for mobile, low vision and cognitive accessibility to WCAG 2.0, and it is the standard named in the US Department of Justice rule for state and local government websites, in EN 301 549 V3.2.1 and in most accessibility settlements.

This checker runs the free scan with the WCAG 2.1 AA preset, so the results match the standard your contract, policy or regulator is most likely to name for a React site.

In React apps, WCAG 2.1 issues are usually in dynamic behavior: toasts and validation messages without a live region, custom inputs without autocomplete, and tooltips that cannot be dismissed with Escape.

Who Should Run the React WCAG 2.1 Checker

• React site owners whose contracts or policies name WCAG 2.1 AA.
• State and local government bodies, under the ADA Title II rule.
• Businesses responding to an ADA demand letter, which usually cites WCAG 2.1 AA.
• Public sector bodies in the EU, under the Web Accessibility Directive.

WCAG 2.1 Criteria That Often Fail on React

• 1.3.5 Identify Input Purpose

  Form fields that collect personal data, such as name, email and address, need the right autocomplete attribute.

• 1.4.10 Reflow

  Content must reflow at 320 CSS pixels wide, the same as 400% zoom, without scrolling in two directions.

• 1.4.11 Non-text Contrast

  Buttons, form borders, icons and focus indicators need a contrast ratio of at least 3:1.

• 1.4.12 Text Spacing

  Text must stay readable when users increase line, paragraph, letter and word spacing.

• 1.4.13 Content on Hover or Focus

  Tooltips and menus that appear on hover or focus must be dismissible, hoverable and stay visible.

• 4.1.3 Status Messages

  Messages such as “added to cart” or form errors must be announced to screen readers without moving focus.

Where React Sites Usually Fail WCAG 2.1

These problems come up again and again on React sites, and each one fails WCAG 2.1. The React accessibility checker explains how to fix them in React.

• Clickable divs and spans. Elements with an onClick handler but no button or link semantics cannot be reached with Tab or activated with Enter and Space, and are not announced as controls.
• Inputs without labels. Fields that use placeholder text, or a label that is not connected with htmlFor, have no reliable accessible name.
• Focus after updates. When a route changes, a modal opens or an item is deleted, focus stays on an element that no longer exists unless the app moves it deliberately.
• Silent updates. Results lists, toasts, form errors and loading indicators change on screen without a live region or other announcement.
• Wrapper divs breaking structure. Extra wrapper elements around list items, table rows and definition lists, added to satisfy JSX, break the semantics. Fragments avoid them.

Worried about ADA claims as well? The React ADA compliance checker covers the React risks behind most complaints.

What to Test by Hand on React

Automated testing finds many, but not all, WCAG 2.1 failures. Check these yourself after the scan:

1. Zoom to 400% and check nothing is cut off or needs scrolling in two directions (1.4.10).
2. Apply increased text spacing with a bookmarklet and check text is still readable (1.4.12).
3. Open hover menus and tooltips and check you can dismiss them with Escape (1.4.13).
4. Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.

Start 3-day free trial

Related Guides

• WCAG 2.1 AA CheckerThe WCAG 2.1 standard in full, for any website.
• WCAG 4.1.2 Name, Role, Value Explained in Plain EnglishWCAG 4.1.2 Name, Role, Value explained simply: give every control a name, role and state with native HTML and ARIA, with code examples and how to test.
• WCAG 3.3.2 Labels or Instructions Explained in Plain EnglishWCAG 3.3.2 Labels or Instructions explained simply: visible labels, format hints, grouped fields and required markers, with code examples and a test routine.
• Automated vs Manual Accessibility Testing: Where Each FitsWhat automated accessibility testing catches, what needs a human, and how to combine both into a repeatable process for finding and fixing WCAG issues.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

React WCAG 2.1 Checker: Frequently Asked Questions