React Section 508 Checker

Section 508 for React Sites

Section 508 of the Rehabilitation Act requires federal agencies to make the information and communication technology they develop, buy, maintain or use accessible. The Revised 508 Standards, in effect since January 2018, incorporate WCAG 2.0 Level A and AA for web content, electronic documents and software.

Private businesses are not directly covered, but agencies must buy accessible technology, so vendors are often asked for an Accessibility Conformance Report (ACR) based on the VPAT. This checker runs the scan with the WCAG 2.0 AA preset that Section 508 uses.

Federal apps built with React are software as well as web content under Section 508. Scan the rendered pages here, and test keyboard and screen reader behavior in your components by hand.

Who Should Run the React Section 508 Checker

• Federal agencies running a site or microsite on React.
• Contractors and vendors whose React site or portal is part of a federal contract.
• Agencies and vendors preparing a VPAT or Accessibility Conformance Report.
• State bodies and universities whose policies adopt Section 508.

Section 508 Checks That Matter for React Sites

• 1.1.1 Non-text Content

  Every image, icon and chart needs a text alternative, or must be marked as decorative.

• 1.3.1 Info and Relationships

  Headings, lists, tables and form labels must be marked up so assistive technology can read the structure.

• 1.4.3 Contrast (Minimum)

  Text needs a contrast ratio of at least 4.5:1, or 3:1 for large text.

• 2.1.1 Keyboard

  Every function must work with a keyboard alone.

• 2.4.1 Bypass Blocks

  Provide a way to skip repeated navigation, such as a skip link.

• 4.1.2 Name, Role, Value

  Custom controls need a name, role and state that assistive technology can read.

Where React Sites Usually Fail Section 508

These problems come up again and again on React sites, and each one fails Section 508. 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, Section 508 failures. Check these yourself after the scan:

1. Test every page with a keyboard only, including menus and dialogs (2.1.1).
2. Check documents and PDFs separately, since Section 508 covers them too.
3. Record results per criterion if you need to complete a VPAT or ACR.
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

• Section 508 CheckerThe Section 508 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 Section 508 Checker: Frequently Asked Questions