Accessibility & Section 508

Everything we deliver is built and tested to WCAG 2.1 AA or better, and we can bring existing sites and applications up to standard. Accessibility is part of our definition of done, not a line item.

Why it matters

For public agencies, accessibility is a legal requirement. Section 508 covers federal agencies and the systems they buy, and the Department of Justice's 2024 ADA Title II rule adopts WCAG 2.1 AA as the standard for state and local government web content and mobile apps. An inaccessible launch is a liability. We remove that risk by testing the way people actually use the software, with a keyboard and a screen reader, and by fixing problems in the code itself.

WCAG 2.2 AASection 508ADA Title IIVPAT 2.5NVDAaxe-core

What we deliver

  • WCAG 2.2 / 2.1 Level AA and Section 508 audits of websites and web applications
  • Keyboard, zoom, and NVDA screen reader testing by a person, not just a scanner
  • Remediation in your templates, components, and content, with no overlay widgets
  • VPAT 2.5 Accessibility Conformance Reports (WCAG and Section 508 editions)
  • Before-and-after reports and an accessibility statement for your site
  • Scheduled monitoring that catches new issues as content changes
  • Accessible components and accessibility checks in our own QA for every project
Built by SiteHatchery

Audsey

We built Audsey, our accessibility testing and remediation service, so our accessibility work is repeatable and provable. Audsey runs four testing engines (axe-core, IBM Equal Access, its own checks, and the browser accessibility tree) at desktop and phone sizes, then a person verifies the results with a keyboard and the NVDA screen reader. Fixes go into the site's own code and content, and every pass produces a before-and-after report.

  • WCAG 2.2 AA, 2.1, 2.0 and Section 508
  • VPAT 2.5 conformance reports
  • Real fixes, never overlay widgets
  • Monthly or quarterly monitoring
Learn about Audsey
Audsey result card from November 2026: accessibility index raised from 65.4 before to 100 after, with 37 issues fixed, 0 errors left open, and 42 WCAG criteria met on a Northern California builder's website.
How we work

Our approach

Built in, not bolted on

Semantic markup, focus management, labels, and contrast are part of how we build, and part of code review.

Tested like it is used

Four automated engines plus a person with a keyboard and a screen reader on every page.

Documented for procurement

Dated reports and VPAT conformance reports your procurement officer and counsel can read.

Track record

Where we have done this

  • Took a Northern California builder's WordPress site from an accessibility index of 65.4 to 100: 37 issues fixed, 58 photos described, 10 pages screen-reader tested.
  • Reviewed a client's website with WAVE and keyboard testing, then fixed color contrast, form labels, heading structure, and keyboard focus.

See our past performance

Insights

Related reading

Related capabilities

Need experienced engineers on a defined scope?

Tell us about the system, the deadline, and the constraints. We will tell you honestly whether we are the right fit.