code/+/trust primary logo full color svg

Section 508

Definition

Section 508 requires federal agencies to buy, build and use accessible technology that meets the Access Board's Revised 508 Standards, which adopt WCAG 2.0 AA.

Section 508 is not optional for any software sold to or used by the federal government. The Revised Section 508 Standards (2017) align with WCAG 2.0 Level AA and cover web content, software, hardware, support services, and documents.

Key Section 508 requirements for software

  • All UI components operable by keyboard alone (no mouse required)
  • Screen reader compatibility (ARIA labels, semantic HTML, focus management)
  • Sufficient color contrast (4.5:1 for normal text, 3:1 for large text)
  • Captions for all video content; audio descriptions for visual-only content
  • No content that flashes more than 3 times per second (seizure risk)

Testing for 508 compliance

Automated tools (axe, Lighthouse, WAVE) catch 30-40% of 508 issues. The remainder require manual testing with screen readers (JAWS, NVDA, VoiceOver) and keyboard-only navigation. Build 508 testing into CI/CD -- axe-core integrates with Jest and Playwright for automated accessibility regression detection.

Related terms

See how we implement this

Need help implementing this in your business?

Code and Trust translates AI concepts like section 508 into working implementations, starting with a workflow audit that shows exactly where it creates ROI.

Schedule AI Audit →