Federal vendors who submitted accessibility documentation in 2024 and expected it to clear procurement review in 2026 are discovering a gap: reviewers are now asking not just whether a product was tested, but how it was tested, which pages and workflows were covered, what version was tested, and whether there is an active remediation plan. A section 508 compliance checker used once before a contract bid is no longer sufficient documentation.
Section 508 of the Rehabilitation Act requires federal agencies and any organization receiving federal funding to ensure their electronic content and software is accessible to people with disabilities. The standard has been referenced in federal procurement, grant compliance, and enforcement for decades — but the scrutiny it receives in 2026 is materially higher than it was even two years ago.
Here's what Section 508 actually requires, which tools to use for testing, what automated section 508 compliance checkers miss, and how to document compliance in a way that withstands federal review.
What Section 508 Requires
Section 508 was updated in 2018 through the "ICT Final Rule," which harmonized U.S. federal accessibility standards with WCAG 2.0 Level AA and EN 301 549 (the European standard). In practice, federal agencies now expect and enforce WCAG 2.1 Level AA, reflecting updates to the European standard and the evolving DOJ interpretation applied to ADA cases.
The standard applies to: - Federal agency websites and web applications - Intranet portals and internal employee-facing tools - Electronic documents (PDFs, Word files, spreadsheets) - Software and mobile applications used by federal employees or the public - Kiosks, hardware with displays, and multimedia content - Any electronic content procured with federal funds or developed under federal contract
Who must comply: All federal executive branch agencies. State agencies receiving federal grants (under Section 504 of the Rehabilitation Act). Any private vendor or contractor selling electronic products or services to the federal government.
The Section 508 Testing Methodology
The General Services Administration and U.S. Access Board administer the Trusted Tester 5.1 program — the official federal framework for Section 508 conformance testing. Trusted Tester is a standardized, reproducible testing methodology that requires:
- Automated testing using approved tools
- Manual keyboard testing across all interactive elements
- Screen reader testing with specific AT/browser combinations (JAWS + Chrome, NVDA + Firefox)
- Testing against specific workflows — not just static pages
Trusted Tester certification (available through DHS) trains testers to apply this methodology consistently. Federal procurement now increasingly requires Trusted Tester-certified testers for accessibility documentation rather than just any automated tool output.
Section 508 Compliance Checker Tools
| Tool | Type | Section 508 Coverage | WCAG Version | Cost |
|---|---|---|---|---|
| ADAGuard | Full DOM scanner | ✅ All plans | WCAG 2.2 AA | Free tier available |
| Accessibility Insights for Web | Extension + guided tests | Partial | WCAG 2.1 | Free (Microsoft) |
| axe DevTools | Extension + full scan | Partial | WCAG 2.1/2.2 | Free + Paid |
| Pa11y | CLI / CI pipeline | Automated only | WCAG 2.1 | Open source |
| Lighthouse | Chrome DevTools built-in | Partial (~42% coverage) | WCAG 2.1 | Free |
| SortSite | Full site crawler | ✅ | WCAG 2.1/2.2 | Paid |
| DHS ANDI | Browser bookmarklet | Manual guide | Section 508 specific | Free |
Automated tools run against the live rendered DOM and flag machine-detectable violations. They're fast, scalable, and catch the structural issues — missing alt text, unlabeled form inputs, low color contrast, missing heading structure, duplicate IDs.
ANDI (Accessible Name & Description Inspector) is DHS's own Section 508 testing tool. It's a browser bookmarklet that inspects the accessibility tree of any page, making it the closest thing to an "official" automated section 508 compliance checker endorsed by the federal program. It's used in Trusted Tester training.
Accessibility Insights for Web (Microsoft) combines automated axe-core scanning with structured guided manual tests organized around the Section 508 technical requirements. Its "Assessment" mode walks testers through 20+ manual test procedures that closely align with Trusted Tester's methodology.
A full scanner like ADAGuard covers approximately 78% of WCAG 2.2 AA criteria automatically using 22 custom check categories plus axe-core integration — compared to approximately 42% for Lighthouse and 40% for WAVE. For Section 508 documentation, the higher automated coverage provides a stronger baseline before manual testing.
What Automated Section 508 Checkers Don't Cover
Automated tools catch structural and measurable accessibility failures. The Trusted Tester 5.1 methodology identifies 63 test conditions — only a portion of which can be verified automatically.
Failures that require manual testing:
1.2.x Multimedia — Captions, audio descriptions, and sign language interpretation for pre-recorded and live media require human review of the actual media content. No tool can verify caption accuracy.
2.1.1 Keyboard — complex interactions — Automated tools can verify that interactive elements are in the tab order. They cannot verify that keyboard interaction is logically correct for complex components like drag-and-drop interfaces, custom date pickers, or data grids.
2.4.3 Focus Order — Tools flag obvious tab-order anomalies. Subtle focus order issues in complex SPAs — where tab sequence is logical according to the DOM but confusing in the visual layout — require manual inspection.
3.1.1 Language of Page / 3.1.2 Language of Parts — While the page lang attribute is machine-checkable, language tagging of individual text passages in a different language (e.g., a French quotation on an English page) requires human review.
Screen reader compatibility — The final test of Section 508 conformance is whether the product actually works correctly with JAWS and NVDA in the specified browser combinations. This cannot be automated — it requires a trained screen reader user navigating actual user workflows.
What Federal Reviewers Expect in 2026
Federal procurement reviewers as of early 2025 began requesting more specific documentation from vendors claiming Section 508 conformance. High-scrutiny areas include:
- Testing scope — Which pages or application screens were tested? Did testing cover the complete workflows, or just representative pages?
- Testing methodology — Was Trusted Tester 5.1 used? Were any manual tests performed?
- Product version — What version was tested? Is the tested version the same as what's being delivered?
- Issue tracking — What violations were found, and what is the remediation plan and timeline?
- Recency — Was testing done within the last 12 months? Products that only have testing documentation from two or more years ago may be flagged.
Vendors who submit a Voluntary Product Accessibility Template (VPAT) — now called an Accessibility Conformance Report (ACR) — with only generic "supports" claims and no documentation of testing methodology are receiving greater pushback than in prior cycles.
How Section 508 Relates to ADA and WCAG
The three standards — Section 508, ADA, and WCAG — are related but distinct:
Section 508 applies specifically to federal agencies and their procurement. Enforcement is through the U.S. Access Board and agency-level compliance programs.
ADA Title II applies to state and local governments and explicitly requires WCAG 2.1 AA (per the 2024 DOJ rule). ADA Title III applies to private businesses open to the public. The DOJ enforces ADA through investigation and litigation.
WCAG is the technical standard that both Section 508 (via the 2018 ICT Final Rule) and the DOJ's ADA enforcement reference. Passing WCAG 2.1 AA is the practical goal for complying with all three.
For organizations navigating multiple obligations — for example, a private healthcare company that has federal contracts AND serves the public — the overlap means that WCAG 2.1 AA is the single standard that satisfies all three requirements simultaneously.
Building a Section 508 Compliance Program
One-time testing does not constitute a compliance program. Federal guidance, ADA settlement terms, and accessibility best practices all point toward the same conclusion: accessibility is maintained through ongoing monitoring, not point-in-time audits.
A practical Section 508 compliance program includes: - Automated scanning on every staging build before deployment - Scheduled production scans to catch regressions from updates - Manual Trusted Tester evaluation on new features and high-traffic workflows - VPAT/ACR documentation updated at each major product version - Staff training for developers and content editors on WCAG authoring practices - An accessible feedback mechanism for users to report barriers
The 30-Second Fix
Run your site through the ADAGuard ada compliance checker — free, no signup. The scan covers Section 508-relevant issues across 22 automated check categories with WCAG 2.2 AA coverage of approximately 78%. The report gives you WCAG criterion references for each violation — exactly the information you need to start a VPAT/ACR entry or a developer remediation ticket. Paste your URL, see what the automated pass catches, then plan your manual testing scope around the results.