Skip to main content
Base22

Analytics cookies

We’d like to use Google Analytics cookies to learn how this site is used and improve it. Nothing is set unless you accept, and there are no advertising cookies. Change your mind anytime under “Cookie settings” in the footer. Privacy policy

Accessibility audits

We test your websites, portals and apps against WCAG 2.1 or 2.2 AA with automated tools, manual review and assistive technology. You get every issue ranked, the fix explained and a retest that shows it worked.

Schematic — client UI under NDA

  • Keyboard and focus
  • Contrast
  • Screen reader labels

Trusted by

  • State of Ohio
  • Stanford University

An audit is only useful if it changes what ships. We test the templates and components your pages are built from, so one fix lands everywhere they are used, and we test the journeys people actually take, with a keyboard and a screen reader, not only a scanner.

The work draws on a record you can check: accessibility and SEO audits across thousands of pages for the Ohio Department of Job & Family Services (2022–2023), the accessible theme we implemented on Liferay for Stanford University’s AXESS portal (2022), and Tech4Me, built to WCAG 2.1 AAA (2025–2026).

01What we deliver

Findings your team can act on.

  • Automated scans at scale

    Every page crawled and checked, so the audit covers the whole site, not a sample.

  • Manual and assistive-technology testing

    Key journeys tested with a keyboard and a screen reader: the issues scanners miss.

  • Findings by component

    Issues traced to the template or component that causes them, so one fix covers every page.

  • A ranked remediation plan

    Every issue with its WCAG criterion, who it blocks, how to fix it and in what order.

  • Retest and evidence

    We retest after the fixes and record what changed, so you can show the result.

  • Checks in your pipeline

    Automated checks on every change, as we run for base22.com at WCAG 2.2 AA.

02How an engagement runs

From scope to a retest you can show.

  1. Scope

    Agree the standard (WCAG 2.1 or 2.2, AA or AAA), the sites and the journeys that matter most.

  2. Test

    Automated scans across every page, then manual and assistive-technology testing of key journeys.

  3. Report

    Findings by component and criterion, ranked, with the fix explained for your developers and authors.

  4. Fix and retest

    We fix with your team or alongside it, retest, and set up checks so the result holds.

03

Related work

Bring us the hard problem.

Book 30 minutes with the senior people who would do the work.

Or write to info@base22.com