RatedWithAI
Accessibility scanner
Federal accessibility conformance just dropped to 1.74 out of 5 — the lowest ever recorded. Section 508 of the Rehabilitation Act requires federal agencies and their contractors to make all information and communications technology (ICT) accessible to people with disabilities. With the April 2026 ADA Title II deadline amplifying urgency, this guide covers everything you need: requirements, compliance checklist, testing methods, PDF accessibility, Section 508 vs WCAG differences, certification options, and enforcement realities.
Section 508 is part of the Rehabilitation Act of 1973, a landmark civil rights law that prohibits discrimination based on disability in programs conducted by federal agencies. Specifically, Section 508 addresses information and communications technology (ICT) — requiring that all technology the federal government develops, procures, maintains, or uses must be accessible to people with disabilities.
The law was first added as an amendment in 1986, but it wasn't until the Workforce Investment Act of 1998 that Section 508 gained real enforcement teeth. That amendment created a mandatory standard — not just a guideline — that federal agencies must follow.
In January 2017, the U.S. Access Board published the most significant update to Section 508 in nearly 20 years — commonly called the "508 Refresh." Effective January 18, 2018, it fundamentally changed how compliance is measured:
The refresh also updated the Federal Acquisition Regulation (FAR) — meaning every federal contract involving ICT must include Section 508 compliance requirements. This is codified in FAR 39.2.
In January 2025, GSA published the second annual governmentwide Section 508 assessment — mandated by the Consolidated Appropriations Act of 2023. The results are alarming: federal conformance fell from 1.79 to 1.74 on a 5-point scale, the lowest ever recorded.
Why conformance is declining while maturity improves: GSA identified a critical gap — agencies are building better programs (hiring 508 coordinators, creating policies, conducting training) but haven't deployed the testing resources needed to actually find and fix violations. Many rely solely on automated scanning, which catches only 30-40% of issues. Without manual testing and assistive technology evaluation, the other 60-70% goes undetected.
The assessment also noted that many agencies don't have staff trained in comprehensive manual testing. Training maturity saw the highest year-over-year increase (+31%), but it's starting from a low base of 1.57 and has reached only 2.06 — still barely "moderate."
Section 508 applies to a much broader range of organizations than most people realize. The "federal nexus" — any connection to federal government funding, contracts, or programs — can bring your organization under its umbrella.
All executive branch agencies, independent regulatory agencies, the Postal Service, and the Postal Rate Commission. All ICT they develop, procure, maintain, or use must be accessible.
Any company that builds, sells, or maintains ICT products for the federal government. The FAR requires Section 508 compliance in all ICT contracts. Without an adequate VPAT/ACR, your product won't even be considered.
State agencies, universities, non-profits, and other organizations receiving federal grants, loans, or other financial assistance have Section 504 obligations that mirror Section 508 requirements for their digital assets.
While Section 508 is technically federal-only, Section 504 requires any program receiving federal money to be accessible. Nearly all state/local governments receive some federal funding.
DoD contracts increasingly require Section 508 compliance. DISA has specific accessibility testing requirements for all delivered systems, and the DoD CIO enforces compliance through procurement review.
Hospitals and health systems receiving Medicare/Medicaid funding (virtually all of them) have Section 504 obligations covering patient portals, telehealth platforms, and EHR systems.
Even if your organization isn't a federal agency, the "federal nexus" can bring you under Section 508's umbrella. If you receive federal grants (research universities, state Medicaid programs, transportation agencies), bid on federal contracts (SaaS vendors, IT consultancies), or participate in federally-funded programs, your ICT must meet Section 508 standards. In practice, this covers tens of thousands of organizations beyond the federal government itself.
Section 508 and WCAG are frequently confused — and for good reason. Since the 2017 refresh, Section 508 directly incorporates WCAG. But they're fundamentally different things, and understanding the distinction matters for compliance planning.
Section 508 currently references WCAG 2.0 Level AA (38 criteria). But the 2024 ADA Title II rule references WCAG 2.1 Level AA (55 criteria). The 17 additional criteria in WCAG 2.1 primarily address mobile accessibility, low vision, and cognitive disabilities. If your organization falls under both Section 508 and ADA Title II — which most state agencies and many federal grant recipients do — you must meet the higher WCAG 2.1 AA standard. The Access Board is expected to update Section 508 to reference WCAG 2.1 or 2.2 in the near future.
For a deeper comparison of WCAG versions, see our WCAG 2.1 vs 2.2 comparison guide and the DOJ's recent position that WCAG is not the ADA standard.
A comprehensive Section 508 compliance checklist covers four categories of ICT. Use this as your baseline audit framework — each item maps to specific WCAG 2.0 AA criteria or Section 508 functional performance criteria.
For a printable checklist focused on web content, see our ADA Compliance Checklist 2026 and WCAG 2.2 Checklist.
Effective Section 508 testing combines three approaches. No single method catches everything — the FY24 assessment specifically called out over-reliance on automated scanning as a driver of declining conformance.
Automated tools are the fastest starting point — they can scan hundreds of pages in minutes and identify common violations like missing alt text, contrast failures, and missing form labels. However, they cannot evaluate content quality, keyboard behavior, or screen reader experience.
AI-powered scanner that tests against both WCAG 2.0 AA (Section 508) and WCAG 2.1 AA (ADA Title II) simultaneously. Provides a compliance score, violation counts, and prioritized fix recommendations.
Try free scan →Open-source accessibility engine used by most automated testing tools. Zero false positives by design. Powers browser extensions, CI/CD integrations, and the new MCP server for AI-assisted testing.
Browser extension that visually overlays accessibility issues on the page. Excellent for manual review of individual pages. Free for individual use.
Built into Chrome DevTools. Runs axe-core checks as part of a broader performance/SEO audit. Good for developer workflows but limited accessibility coverage.
Open-source CLI tool for automated accessibility testing. Ideal for CI/CD pipelines. Supports HTML CodeSniffer and axe-core engines.
See our full comparison of accessibility testing tools for detailed reviews of 12 tools.
Manual testing is where most violations are actually found. Focus on these key areas:
The DHS Trusted Tester process requires testing with actual assistive technologies:
Free, open-source screen reader. The primary tool in the DHS Trusted Tester process. Most popular for testing.
Industry-standard commercial screen reader. Most widely used by blind computer users. Essential for enterprise testing.
Built into Apple devices. Critical for testing iOS and macOS applications.
Built into Android devices. Required for testing Android mobile applications.
Free web accessibility testing tool from the Social Security Administration. Tests data tables, links, images, structure, and more.
RatedWithAI scans your website against WCAG 2.0 AA (Section 508) and WCAG 2.1 AA (ADA Title II) standards simultaneously. Get a compliance score, violation counts, and prioritized fix recommendations in seconds.
PDF documents are one of the most common Section 508 failure points. An estimated 95% of government PDFs are not fully accessible — making this the single largest category of non-compliance in federal ICT. The FY24 assessment found that document testing coverage declined significantly from the prior year.
Section 508 requires electronic documents — including PDFs — to meet WCAG 2.0 Level AA. This means:
Every PDF must be tagged with semantic markup — headings, paragraphs, lists, tables, and reading order. Tags tell screen readers what each element is and how to read it. An untagged PDF is essentially invisible to assistive technology.
All non-decorative images must have alt text that conveys the same information as the visual. Charts and graphs need detailed descriptions. Decorative images should be marked as artifacts so screen readers skip them.
The tag structure must follow the visual reading order. Multi-column layouts, sidebars, and callout boxes must be tagged in the order a sighted reader would encounter them. This is where most PDFs fail.
Data tables must have header cells (<TH>) with scope attributes. Complex tables with merged cells need ID/header associations. Layout tables should be avoided entirely.
The PDF's metadata must specify the document language (e.g., English). Content in other languages must be tagged with the appropriate language attribute.
PDFs longer than 9 pages should have bookmarks corresponding to the heading structure. This provides a navigation aid similar to a table of contents.
All form fields must have labels, instructions, and proper tab order. Required fields must be indicated. Error messages must be programmatically associated with the field.
Text in PDFs must meet the same 4.5:1 contrast ratio as web content. Information must not be conveyed by color alone.
The most reliable way to meet Section 508 requirements for documents is to publish content as accessible HTML web pages instead of PDFs. HTML is natively supported by assistive technology, responsive by default, and easier to test and maintain. Reserve PDFs only for content that genuinely requires fixed-format layout (legal filings, signed forms, print-ready materials). Section508.gov itself recommends this approach.
There is no official government certification for Section 508 compliance. Unlike ISO standards, there is no certifying body that can stamp your product or website as "508 Certified." However, several related certifications and documentation approaches exist:
What: Certifies that an individual can conduct standardized Section 508 conformance testing
Who: Federal employees and contractors who test ICT for Section 508
How: Complete DHS Trusted Tester training and pass the certification exam. Covers NVDA, ANDI, and the ICT Testing Baseline.
What: Standardized documentation of how a product conforms to Section 508 standards
Who: Any vendor selling ICT to the federal government
How: Complete the VPAT template (published by ITI) for your product. Four editions available: WCAG, 508, EU, and International.
What: Professional certifications for accessibility practitioners
Who: Accessibility professionals, UX designers, developers, QA testers
How: CPAC (Certified Professional in Accessibility Core) covers fundamentals. WAS (Web Accessibility Specialist) focuses on WCAG technical implementation.
What: Independent evaluation by a recognized accessibility firm
Who: Organizations seeking credible verification of their 508 compliance claims
How: Hire a reputable accessibility consulting firm (Deque, Level Access, TPGi, WebAIM) to conduct a comprehensive audit. They provide a report with findings and recommendations.
What: Machine-readable accessibility conformance reports
Who: Technology vendors selling to the federal government
How: Create an ACR in a standardized, machine-readable format. GSA hosts the OpenACR repository for public access. This is the future direction for VPAT documentation.
For a deep dive into VPATs and ACRs, see our complete VPAT guide and downloadable VPAT templates.
While Section 508 has been in effect since 2001 (with the 2017 refresh effective January 2018), the upcoming April 24, 2026 ADA Title II deadline creates unprecedented urgency for organizations that overlap both laws.
Must comply with both Section 508 (via Section 504) AND ADA Title II WCAG 2.1 AA. The ADA rule is stricter — WCAG 2.1 adds 17 criteria beyond WCAG 2.0 (mobile, low vision, cognitive).
Federal research grants trigger Section 508. State funding triggers ADA Title II. Both now apply, and the higher standard (WCAG 2.1 AA) effectively becomes the floor.
Your government clients now face the April 2026 deadline. If your product isn't WCAG 2.1 AA compliant, they can't deploy it. This is an active contract risk.
Medicare/Medicaid funding triggers Section 504/508. Hospital websites serving 50K+ populations also face ADA Title II. Double exposure requires the higher standard.
Bottom line: If your organization is subject to Section 508, you should already be targeting WCAG 2.1 Level AA — not just WCAG 2.0 — to future-proof compliance. Read our ADA Title II deadline countdown guide for the full timeline.
Section 508 enforcement has historically been weaker than ADA Title III enforcement, but that's changing — especially since the Consolidated Appropriations Act of 2023 mandated annual assessments.
Federal procurement officers can reject products without adequate VPATs, cancel contracts for non-compliance, or require remediation at the vendor's expense. In 2024, GSA removed 12 products from IT Schedule 70 for missing or inaccurate VPATs.
While Section 508 itself doesn't create a broad private right of action, Section 504 does. Organizations receiving federal funding can be sued for inaccessible ICT. Recent settlements include $2M+ in damages against a state Medicaid portal.
The DOJ can investigate and sue federal agencies and federally-funded organizations. In 2025, DOJ settled with three federal agencies over inaccessible employee-facing systems — remediation costs exceeded $15M combined.
Federal employees and members of the public can file complaints with any agency. Since 2023, the DOJ has been more aggressive in tracking complaint resolution.
The 2023 appropriations amendment now requires annual assessments reported to Congress. Poor performers face public scrutiny and potential budget impacts. GSA publishes full agency-by-agency results.
For the financial implications, see our government compliance cost comparison and IRS tax credit guide for accessibility costs.
Whether you're a federal agency, a vendor selling to the government, or an organization receiving federal funding, here's a practical roadmap to achieve and maintain Section 508 compliance:
Use RatedWithAI, axe-core, or WAVE to scan your top 20 pages. This gives you a severity-ranked list of the most common violations in under 5 minutes. Focus on pages with the highest traffic and those used in procurement demonstrations.
⏱ 30 minutesTab through your top 5 pages using only the keyboard. Then test with NVDA (free) on Windows or VoiceOver (built-in) on macOS. Document where you get stuck, where focus disappears, and where content is announced incorrectly.
⏱ 2-4 hoursAddress Critical issues first (keyboard traps, missing alt text on functional images, inaccessible forms), then High (contrast failures, heading hierarchy), then Medium (minor ARIA issues, decorative image tagging). The Pareto principle applies: 20% of fix types resolve 80% of violations.
⏱ 1-4 weeksAudit your PDF inventory. Convert high-traffic documents to HTML where possible. For remaining PDFs, run them through Adobe Acrobat's accessibility checker, add tags, set reading order, and add alt text. Consider using CommonLook or PAC 2024 for bulk remediation.
⏱ 2-8 weeksIf you sell to the federal government, document your conformance in a VPAT. Be honest about partially supported criteria — procurement officers respect transparency over inflated claims. Use the ITI VPAT 2.5 template and consider the INT (International) edition for broadest coverage.
⏱ 1-2 weeksSection 508 is not a one-time project. Set up automated scans to run with each deployment or at minimum weekly. Conduct manual testing quarterly. Do a full comprehensive audit annually. CMS updates, new content, and third-party integrations can introduce new violations at any time.
⏱ OngoingDevelopers, designers, content creators, and procurement officers all need Section 508 awareness training. The FY24 assessment showed training maturity improved 31% — the biggest improvement of any dimension — because agencies finally invested in it.
⏱ OngoingOur free scanner tests your website against WCAG 2.0 AA (Section 508) and WCAG 2.1 AA (ADA Title II) simultaneously. Get your compliance score in under 60 seconds.
Related reading: VPAT Guide & ACR Creation · ADA Title II Deadline Countdown · DOJ: WCAG Is Not the ADA Standard · WCAG 2.1 vs 2.2 Comparison · Best Testing Tools Compared · How to Fix Common WCAG Failures · FTC Fined accessiBe $1M · European Accessibility Act Guide · Lawsuit Statistics 2026 · NASCIO State Government Report · School District Compliance Guide · Higher Education Compliance Guide