Federal agencies
Every agency website, intranet, app and document must meet Section 508.
Check your site against the WCAG 2.0 AA rules Section 508 uses, give visitors accessibility controls today and track every fix in one dashboard.
Not sure where your site stands? Scan it free

WCAG 2.0 AA
Standard Section 508 uses
Jan 2018
Refreshed rules apply since
16
Visitor tools
Overview
Section 508 of the Rehabilitation Act requires US federal agencies to make the information and communication technology (ICT) they build, buy and use accessible to people with disabilities. That includes websites, web apps, software and electronic documents such as PDFs.
Since the refresh that took effect in January 2018, Section 508 points to WCAG 2.0 Level A and AA for web content. In practice, Section 508 compliance for a website means meeting those WCAG 2.0 AA success criteria and being able to show it, usually in an Accessibility Conformance Report (ACR) based on the VPAT template.
Inclusense is accessibility software that combines both sides: scans that show what to fix in your code, and compliance widgets that give visitors controls today.
Page preview
The embed does not change your stack — it adds the same panel customers configure in the dashboard.
Launcher ready
A small button sits on every page of your site.
Scope
Section 508 applies to federal agencies, and the same standard reaches many of the organisations they work with.
Every agency website, intranet, app and document must meet Section 508.
Vendors selling ICT to federal agencies are usually asked for a Section 508 ACR or VPAT.
Many institutions that receive federal funding adopt Section 508 or WCAG AA in their accessibility policy.
Many states have their own Section 508-style laws, and ADA Title II rules point public entities to WCAG 2.1 AA.
Section 508 compliance checklist
The WCAG 2.0 AA areas a Section 508 audit checks most often.
Text alternativesEvery meaningful image, icon and chart has alt text; decorative images are hidden from screen readers.
Captions and transcriptsPre-recorded video has captions and audio description; audio has a transcript.
Keyboard accessEvery link, button, menu and form works with a keyboard alone, with a visible focus indicator.
Colour contrastBody text has at least 4.5:1 contrast and large text 3:1, and colour is never the only way to show meaning.
Forms and errorsFields have labels and instructions, and errors are described in text, not only by colour.
Structure and headingsPages use real headings, landmarks and lists, with a meaningful order and a page title.
Accessible documentsPDFs, Word files and slides you publish are tagged, readable by screen readers and in a logical order.
Timing and motionUsers can pause, stop or extend moving content and time limits, and nothing flashes more than 3 times a second.
Go through every criterion with our interactive WCAG 2.2 checklist, which includes all WCAG 2.0 AA criteria, or see what changed between WCAG versions.
Section 508 testing
Automated checks find issues fast; manual testing confirms what automation cannot.
A Section 508 compliance checker such as the free Inclusense scan finds missing alt text, low contrast, empty labels and ARIA errors in minutes.
Tab through every page: check focus is visible, the order makes sense and nothing traps the keyboard.
Use NVDA, JAWS or VoiceOver on key pages and flows such as forms, search and checkout.
Test the PDFs and files you publish, since Section 508 covers electronic documents too.
Record results in an ACR (VPAT), fix the issues and rescan after every release.
Comparison
Section 508 is the law; WCAG is the technical standard it uses.
| Â | Section 508 | WCAG |
|---|---|---|
| What it is | A US federal law (Rehabilitation Act, Section 508) | Technical guidelines from the W3C |
| Who it applies to | Federal agencies and the ICT they buy, build and use | Anyone; used by laws such as the ADA, EAA and Section 508 |
| Web standard | WCAG 2.0 Level A and AA | WCAG 2.0, 2.1 and 2.2 (each adds criteria) |
| What it covers | Websites, software, documents, hardware and support docs | Web content and web apps |
| Proof | An ACR (VPAT) is usually required in procurement | No formal report required |
Also need US private-sector rules? See our ADA compliance audit and ADA compliance widget.
How Inclusense helps
Scan up to 5 pages free against WCAG 2.2 AA, which includes the WCAG 2.0 AA criteria Section 508 uses. Issues are ranked by severity.
The widget gives visitors 16 tools for contrast, text, reading and motion while your team fixes the code.
One dashboard for every site: rescan after each release and see which issues are fixed.
Use scan results as a starting point when you write your Accessibility Conformance Report.
Honest limits
No. A widget helps visitors, but compliance depends on your code, content and documents meeting WCAG 2.0 AA.
Compliance widgets
16 tools plus a language selector. Turn each one on or off in your dashboard.


Any platform
One line of code adds the widget to any site, and scans work on any public URL.
On WordPress? Install the free Inclusense plugin from WordPress.org and add visitor controls without editing your theme.
Plans
Start free on sites with up to 10,000 monthly page views. Upgrade for more tools, languages and branding. Scans are priced separately.
| Plan | Monthly views | Tools | Customise | Languages | Branding |
|---|---|---|---|---|---|
| Free$0/mo | Up to 10K | 6 core tools | No | English | Inclusense badge |
| Starter$19/mo | Up to 50K | 11 tools | Yes | Multi-language | Inclusense badge |
| Silver$49/mo | Up to 100K | All 16 tools | Yes | Multi-language + auto-detect | Remove badge, add your logo |
| Gold$69/mo | Up to 1M | All 16 tools | Yes | Multi-language + auto-detect | Remove badge, add your logo |
Starter adds manage brightness, manage saturation, letter & word spacing, cursor size and hide images to the 6 free tools.
Over 1M monthly views? See Platinum and yearly billing on the pricing page.
FAQ
Section 508 compliance means your website, software and documents meet the accessibility standards of Section 508 of the Rehabilitation Act. For web content, that is WCAG 2.0 Level A and AA. It is required for US federal agencies and is often asked of their vendors.
Start with an automated Section 508 compliance checker to find common issues, then test with a keyboard and a screen reader, check your PDFs and record the results in an Accessibility Conformance Report (ACR). Retest after every release.
Section 508 is a US law; WCAG is the set of technical guidelines it uses. Section 508 points to WCAG 2.0 Level A and AA. A site that meets WCAG 2.1 or 2.2 AA also covers those WCAG 2.0 AA criteria.
Federal agencies must comply. Government contractors and vendors are usually asked to show Section 508 conformance in an ACR or VPAT, and many universities and state agencies adopt the same standard in their own policies.
Yes. The free Inclusense Accessibility Widget plugin for WordPress adds visitor accessibility controls without editing your theme. Pair it with a scan to find the code issues Section 508 testing looks for.
No. Compliance depends on your code, content and documents meeting WCAG 2.0 AA. A widget helps visitors adjust the page, but you still need to fix the issues a scan or audit finds.
A VPAT (Voluntary Product Accessibility Template) is a template for reporting how a product meets accessibility standards. Once completed, it is called an Accessibility Conformance Report (ACR). Federal buyers use it to compare Section 508 conformance.
Yes. You can scan up to 5 pages free with no account. Paid audit plans add more pages, scan history and recurring scans.
This page is general information, not legal advice. Last updated:
Scan up to 5 pages free, then add the widget on the free plan. No card needed.