Skip to main content
Mobility Labs
← All services
Accessibility Compliance

Accessibility audits and Section 508 testing for public agencies, schools and nonprofits

An accessibility audit tells you where your website or application fails people who use keyboards, screen readers, magnification or captions, and what to fix first. We test against WCAG 2.1 Level AA, the standard behind the ADA Title II rule, and that same testing covers the WCAG 2.0 criteria that Section 508 references.

You get findings your developers can act on: each issue tied to a WCAG success criterion, where it happens, who it affects and how to fix it.

Start a conversationRead the FAQ

What the audit covers

  • Automated scanning of every page template with axe-core, to catch the issues tools can find reliably
  • Manual review against each WCAG 2.1 A and AA success criterion, which automated tools cannot judge on their own
  • Keyboard-only testing of navigation, menus, forms and dialogs
  • Screen reader testing of key tasks with NVDA and VoiceOver
  • Colour contrast, including text placed over images, where scanners often give no answer
  • Zoom, reflow and mobile layouts
  • Documents such as PDFs, when they are part of the scope

What you get

  • An issue log: WCAG criterion, severity, location, screenshot and recommended fix for each issue
  • A plain-language summary for leadership, with the issues that block people ranked first
  • A criterion-by-criterion conformance overview against WCAG 2.1 AA
  • A retest of the fixes, so you can show progress with evidence

Fixing what we find

We build in React and Next.js, so we can fix the issues ourselves or work alongside your developers. Where the same problem repeats across a site, we fix the shared component once, so it stays fixed.

What an audit can and can’t promise

There is no official ADA or Section 508 certification, and no audit can promise a site is "100% compliant". What we can give you is an accurate, documented picture of conformance to WCAG 2.1 AA, and a site that works better for the people using it.

Frequently asked questions

What is the difference between an automated scan and an audit?

Automated tools find a minority of accessibility issues, such as missing alternative text or low contrast. They can’t tell whether a screen reader user can complete a form or whether focus order makes sense. An audit adds manual and assistive technology testing against every WCAG criterion.

Do Section 508 and the ADA use the same standard?

Not exactly. The Section 508 standards for federal agencies reference WCAG 2.0 Level A and AA. The ADA Title II rule for state and local governments requires WCAG 2.1 Level AA. WCAG 2.1 includes every WCAG 2.0 criterion, so testing to 2.1 AA covers both.

Will an accessibility overlay or widget make our site compliant?

No. Overlays change how a page looks or reads, but they don’t fix the underlying code, and many assistive technology users turn them off. We recommend fixing the issues in the site itself.

How is an audit scoped?

By page templates and key user tasks rather than total page count, because most issues repeat across pages built from the same template. We review your site first and give you a fixed quote.

Related

Ready to discuss your next project?

We'll schedule a 30-minute discovery call to understand your goals, assess fit, and outline next steps — no pressure, no pitch deck.

Start a conversationSee our work