Skip to content
easeweb

Is there a free Section 508 compliance checker?

No tool can tell you a site meets Section 508. Free checkers, ANDI and Readout point to problems; a certified Trusted Tester's manual test decides.

3 A tool settles it Page language, page title, parsing 47 A tool can point, a person decides Labels, focus order, contrast over pictures… 13 Only a person can judge Captions that match the audio, keystroke timing…

In short: No. Section 508 holds web content to WCAG 2.0 Level A and AA, and the Trusted Tester process tests it in 63 test conditions, of which a tool alone can settle 3. Free tools find problems and point to the conditions they touch; the result an agency accepts is a manual test by a certified Trusted Tester, recorded condition by condition.

01

When you need this

A small company sells a web-based booking app. A federal agency wants to buy it, and the contracting officer asks for an ACR against the Revised Section 508 Standards. The product lead searches for a free Section 508 compliance checker, runs one on the sign-in page and the dashboard, and gets 0 errors and a "508 compliant" badge to put in the footer.

The app also has a booking form, a training video in its own player, a page where each customer uploads their logo, and a help centre whose only contact is a phone number. The question is whether the scan can stand behind the ACR.

02

What Section 508 asks of a website

Section 508 of the Rehabilitation Act (29 U.S.C. 794d) applies to federal agencies when they develop, procure, maintain or use information and communication technology. It reaches a company through what the agency buys: the Federal Acquisition Regulation says acquisitions of ICT "shall meet the applicable ICT accessibility standards at 36 CFR 1194.1" (FAR 39.203(a)). Some states hold their own agencies to it as well; California's Government Code section 7405(a) does, for what state entities develop, procure, maintain or use. A private site that sells nothing to a government isn't held to Section 508 itself, though other laws may reach it; those are on which accessibility laws apply to my site.

For a website, the Revised 508 Standards come down to a few provisions:

Provision What it asks Where a website meets it
E205.4, E207.2 WCAG 2.0 Level A and AA success criteria and conformance requirements Every public-facing page, and the content of web applications
501.1 exception A web application with no access to platform accessibility services needn't meet 502 or 503, if it conforms to WCAG 2.0 Level A and AA A site or web app that meets its condition
503.4, 503.4.1, 503.4.2 Controls for captions and audio description, at the same menu level as volume or program selection A video player
504.2, 504.3 An authoring tool lets authors make content that conforms to WCAG 2.0, and prompts them to A CMS, an editor, an upload form
E208.1, 602, 603 Documentation lists the accessibility features; web-based self-service support conforms to WCAG 2.0; support services accommodate communication needs A help centre, a support desk
E204.1, 302 9 functional performance criteria, for any function the requirements in chapters 4 and 5 don't address Case by case

The standard is WCAG 2.0, incorporated by reference. WCAG 2.1 and 2.2 add criteria that Section 508 doesn't require, though a contract can. Content that met the original 508 standards and hasn't been altered on or after 18 January 2018 needn't be modified (E202.2).

03

How a Section 508 test is done

A Section 508 result rests on a chain of documents, each one fixing a different part of the test:

  1. Revised 508 Standards What must be met
  2. ICT Testing Baseline 3.1 What must be tested
  3. Trusted Tester process 5.1.3 How, and with which tools
  4. Certified Trusted Tester Who records each result
  5. ACR What the agency reads

The Trusted Tester process has 63 test conditions, mapped to 41 requirements: 38 WCAG 2.0 Level A and AA success criteria and 3 Section 508 requirements, 503.4, 503.4.1 and 503.4.2, the media player controls. So although 501.1 frees most web applications from 503, a site tested with this process gets results for its player's caption and audio description controls (tests 17.D to 17.G). Every test condition gets one of 4 results, Pass, Fail, Does Not Apply or Not Tested, and "Each Test Condition must have a test result for testing to be considered complete." The process covers web content only; software has its own.

The process calls itself "essentially a code inspection for accessibility properties". Its tools are ANDI, a free open-source bookmarklet from the US Social Security Administration, and the Colour Contrast Analyser; both are free. The tools show the tester names, roles, states and colours, and the tester decides each condition. How a whole site is sampled and reported is on testing a whole site against WCAG, and standing behind the result.

04

What a free tool can settle, and what it can't

Of the 63 test conditions, by EaseWeb's count, a tool alone settles 3: 11.A, that the page has a language; 12.A, that it has a title; and 20.A, parsing. For 47 more, a tool can find likely failures and point at the element, but whether the condition is true takes a person: whether an image's text alternative serves its purpose (7.A), whether focus order keeps the meaning (4.F), whether a label describes its field (5.B). The last 13, such as captions that match the audio (17.A) or no keystroke timing (4.B), only a person can judge.

What each free tool does, and where it stops:

  • ANDI and the Colour Contrast Analyser are the process's own tools, and they show the tester what to judge. They don't record a result.
  • Rule-based checkers such as axe, WAVE and Lighthouse find what a rule can catch. What each is good for is on free accessibility testing tools, and what they miss on what automated checks miss.
  • Readout, EaseWeb's free Chrome extension, runs the checks it can on the page you have open, pressing keys as well as reading the page. Some of its findings name the Trusted Tester condition they touch, such as 13.C for text over a picture, to be measured with the Colour Contrast Analyser, and its list of what a person must check comes from the 63 conditions. It is free to install, and it tells you where to look; it doesn't record a result.

None of them can produce a Section 508 result, because a result is a value for every test condition on the content in scope, and most of them need a person. A "508 compliant" badge from a scanner doesn't fit the process either: an ACR built on Trusted Tester results must identify the test process, the scope and the test environment.

05

Worked example

The booking app, from the scan to the ACR:

What Found by Result
Page language and page title on the 2 pages scanned (11.A, 12.A) The free checker Pass
The date field on the booking form has a placeholder and no label Readout, then the Trusted Tester 5.A and 5.C Fail: form fields with missing or mismatched labels
The training video's captions are in a settings menu; volume is in the control bar The Trusted Tester 17.F Fail (503.4.1): video players with no captions button in the control bar
The logo upload never asks for alt text Checked against 504.3, outside the web process Does not support: image uploads that never ask for alt text
The help centre's only contact is a phone number Checked against 603.3, outside the web process Does not support: support that can only be reached by phone

Result: the scan's 0 errors were true for what it checks. The Trusted Tester's test of the app's pages, with a result for all 63 conditions on each, found 3 failing conditions, and the provisions outside the web process added 2 more rows. The ACR states those, with the process, the scope and the environment, instead of "Supports" everywhere, and the badge comes off the footer.

06

Common mistakes

  • Calling a site "508 compliant" because a scanner passed. A scanner answers a few conditions on the pages it ran on. Record every condition by hand, or say what was tested.
  • Filling in an ACR from a scan. An ACR built on Trusted Tester results must name the test process, the scope and the environment, and a VPAT tested by a scan only is a warning sign to a buyer, as reading a vendor's VPAT before you buy, and what to ask next explains.
  • Reporting a WCAG 2.1 or 2.2 failure as a Section 508 failure. The standards incorporate WCAG 2.0. A failure of a later criterion, such as 2.5.8 Target Size (Minimum), belongs in the report as its own finding, or under the contract that asks for it.
  • Leaving out the player's controls. A web app that meets 501.1's exception is free of 503, but the Trusted Tester process still tests 503.4, 503.4.1 and 503.4.2 on a media player.
  • Testing only the web pages. Documentation and support services are scoped by E208.1, and an upload form that makes web content is an authoring tool under 504.
  • Taking results from an uncertified tester to an agency that uses the process. It accepts results only from certified Trusted Testers.

07

What the standard says

  • E205.4 (required): "Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1)."
  • E207.2 (required): "User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0".
  • 501.1 exception (required): "Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0."
  • 503.4.1 (required): "Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection."
  • 504.3 (required): "Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0", for supported features and file formats.
  • 603.3 (required): "Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities."
  • FAR 39.203(a) (law): "acquisitions for ICT supplies and services shall meet the applicable ICT accessibility standards at 36 CFR 1194.1", unless an exception or exemption applies.
  • The Trusted Tester process (method, not law): a Trusted Tester is "certified to provide accurate and repeatable Revised 508 conformance test results for web content".

The EU's standard, EN 301 549, asks for WCAG 2.1 where Section 508 asks for 2.0; how the two differ is on what EN 301 549 asks of a website beyond WCAG.

08

Limits

This page doesn't settle whether Section 508 applies to a given contract, or whether an exception or exemption does (FAR 39.204 and 39.205); that is for the contracting officer and the company's lawyer. State laws that adopt Section 508 differ in what they cover, so read the state's own text. The Trusted Tester process covers web content only, and the provisions outside it, such as 504 and 603, are tested by other means and reported in the same ACR. No tool on this page, Readout included, produces a conformance result. The result is a certified Trusted Tester's manual test, recorded for every test condition, with its date, scope and environment, and the ACR built on it.

09

Terms

ICT Testing Baseline
The minimum tests a Section 508 test process for web content must include. It is not a test process itself, and it names no tools.
test condition
One statement in the Trusted Tester process that is true or false for the content tested, recorded as Pass, Fail, Does Not Apply or Not Tested.
Trusted Tester
A person certified by the Department of Homeland Security to give Section 508 conformance results for web content, following the Trusted Tester process with its approved tools.
ACR
Accessibility Conformance Report: a completed VPAT, which reports a product against a standard criterion by criterion.

10

Sources and guides

Guides that show it

This page explains a practice, with recreated examples. It is not legal advice, and it is not a finding about a named client.