Skip to content

Accessibility

Accessibility audits and remediation.

We test your site or app against WCAG 2.2 AA with automated scans and hands-on keyboard and screen-reader checks, fix what we find in your codebase, and keep it passing. No overlays, no plug-ins that paper over the problem.

  • WCAG 2.1 and 2.2 AA
  • Section 508
  • EN 301 549
  • Fixes in code

Our own site, audited

vaug.in

22 November 2026 · WCAG 2.2 Level AA

Pages tested
81 × 3 views
Issues fixed
9
Automated failures now
0
Overlays used
None

The full issue log is below, as a sample of what you receive.

Method

Automated scans find the obvious. People find the rest. 

Every audit combines tools that check every page with hands-on testing of the journeys that matter, then fixes go into your code and get re-tested.

  1. 01

    Week 1

    Scope and inventory

    We list every template, page type, component, form, document and third-party embed, and agree the standard (usually WCAG 2.1 or 2.2 AA) and the browsers and assistive technologies to cover.

  2. 02

    Days 2–4

    Automated scans

    axe-core and Lighthouse across every URL in the sitemap, in each theme and at phone width, to catch contrast, labels, landmarks, ARIA and target-size issues at scale.

  3. 03

    Week 2

    Manual testing

    Keyboard-only journeys, NVDA, JAWS and VoiceOver checks, 200% and 400% zoom, 320 px reflow, motion and timing, forms and error messages, PDFs and media. Automated tools find roughly a third of real issues; this finds the rest.

  4. 04

    Weeks 2–4

    Remediate in code

    Fixes go into your codebase as reviewed pull requests, starting with the issues that block tasks. Shared fixes (tokens, components) come first, so one change clears hundreds of instances.

  5. 05

    Ongoing

    Verify and monitor

    We re-test every fix, publish an accessibility statement, and add scans to your release process so regressions are caught before they go live.

What we test

Eight areas, every audit. 

  • Keyboard and focus

    Every control reachable and usable without a mouse, in a logical order, with a visible focus indicator that is never hidden.

  • Screen readers

    Names, roles, states, headings, landmarks and live updates checked with NVDA, JAWS, VoiceOver and TalkBack.

  • Colour and contrast

    Text, icons and focus indicators against WCAG ratios in every theme and state, fixed at the design-token level.

  • Zoom and reflow

    Content at 200% and 400% zoom and at 320 px wide, with no loss of content or two-way scrolling.

  • Motion and timing

    Pause controls for moving content, reduced-motion support and no time limits users cannot extend.

  • Forms and errors

    Labels, instructions, error identification and suggestions, and accessible authentication.

  • Media and documents

    Captions, transcripts and audio description for video; tagged, readable PDFs.

  • Structure and language

    Page titles, heading outline, landmarks, language of page and parts, and consistent navigation.

Sample report

What you receive, shown on our own website. 

This is our real audit of vaug.in: what we found, how each issue was fixed in the code, and how we verified it. Filter it, open any issue.

Sample report · our own website

Accessibility audit: vaug.in

22 November 2026 · WCAG 2.2 Level AA · 81 pages × 3 views

Issues logged
11
Resolved
9
Exceptions
1
Open
0

Instances flagged

19,487before

0after fixes, on re-test

Most instances came from two shared causes: colour tokens and a carousel component. Fixing those cleared them everywhere at once.

Issues by WCAG principle

  • Perceivable3

  • Operable5

  • Understandable0

  • Robust2

How we tested

  • View: Light theme, 1280 px
  • View: Dark theme, 1280 px
  • View: Phone, 390 px
  • axe-core 4.13 (WCAG 2.0, 2.1 and 2.2 A/AA rules plus best practices)
  • Chrome
  • Keyboard only
  • Accessibility-tree review (names, roles, states)

Showing 11 of 11 issues

  • VA-01Text below 4.5:1 contrast1.4.3 Contrast (Minimum) · AAResolved
    Where
    Labels, captions and form hints on every page, and white text on the violet accent. Most instances were inside drawn product screens (see VA-02).
    Found by
    Automated (axe-core)
    Instances
    15,187 before → 0 after
    Fix
    Changed two design tokens instead of patching pages: subtle text is now #69646f on light bands and #918c99 on dark ones (4.5:1 or better on every surface), and the violet accent is #7c4dee (5.1:1 with white).
    Verified
    Full re-scan of every page in light, dark and phone views.
  • VA-02Small text inside drawn product screens1.4.3 Contrast (Minimum) · AAException
    Where
    Case-study product screens and hero mock-ups
    Found by
    Automated (axe-core)
    Rationale
    The screens are pictures of software, so their small interface text counts as text in an image (WCAG's exception for incidental text). Each screen is marked inert, carries a text alternative (its caption) and opens in a zoomable viewer.
    Verified
    Screens are outside the tab order and announced by caption only.
  • VA-03Carousel dots smaller than 24 × 24 px2.5.8 Target Size (Minimum) · AAResolved
    Where
    Product-screen carousels on case-study cards and heroes
    Found by
    Automated (axe-core)
    Instances
    3,240 before → 0 after
    Fix
    Each dot is now a 24 × 24 px button around the same small bar, so the look is unchanged and the target is easy to hit.
    Verified
    Re-scan, plus tap tests at 375, 390 and 430 px.
  • VA-04Extra main landmarks and headings inside mock-ups1.3.1 Info and Relationships · AResolved
    Where
    Drawn screens that contained <main>, <h1> and <h2> elements
    Found by
    Automated (axe-core)
    Instances
    888 before → 0 after
    Fix
    Mock-ups use neutral elements, and the case-study section labels became real h2 headings, so every page has one main landmark and an unbroken heading outline.
    Verified
    Landmark and heading-order rules pass on every page.
  • VA-05Mega-menu links reached only after the rest of the header2.4.3 Focus Order · AResolved
    Where
    Desktop navigation: What We Do, Industries, Engineering, About
    Found by
    Manual (keyboard)
    Instances
    4 before → 0 after
    Fix
    Menus follow the disclosure pattern: Tab from an open menu button enters its links, Tab past the last link moves on, Shift+Tab goes back, and Escape closes the menu and returns focus.
    Verified
    Keyboard walk-through of every menu.
  • VA-06Closed mobile menu still reachable with Tab2.4.3 Focus Order · AResolved
    Where
    Phone navigation
    Found by
    Manual (keyboard)
    Instances
    1 before → 0 after
    Fix
    Closed menus are inert, so hidden links never take focus.
    Verified
    Keyboard walk-through at 390 px.
  • VA-07Moving content with no way to pause it2.2.2 Pause, Stop, Hide · AResolved
    Where
    162 looping CSS animations, plus the ticker, rotating headline words, product carousels and illustrations driven by script
    Found by
    Manual (motion)
    Instances
    162 before → 0 after
    Fix
    A "Pause animations" button in the header stops every looping animation and remembers the choice; carousels also have their own pause button and stop on hover or focus. The operating system's reduce-motion setting does the same automatically.
    Verified
    Checked with the button on and off, and with reduced motion emulated.
  • VA-08Theme switch did not announce whether it was on4.1.2 Name, Role, Value · AResolved
    Where
    Header theme button
    Found by
    Manual (screen reader)
    Instances
    1 before → 0 after
    Fix
    The button exposes its state (aria-pressed) and has a stable name.
    Verified
    Accessibility-tree check of name, role and state.
  • VA-09Screen-reader label on a non-interactive element4.1.2 Name, Role, Value · AResolved
    Where
    Home page wordmark animation
    Found by
    Automated (axe-core)
    Instances
    3 before → 0 after
    Fix
    Replaced the invalid aria-label with visually hidden text.
    Verified
    Re-scan.
  • VA-10Header could hide while a header item had focus2.4.11 Focus Not Obscured (Minimum) · AAResolved
    Where
    Sticky header on scroll
    Found by
    Manual (keyboard)
    Instances
    1 before → 0 after
    Fix
    The header stays in view while it holds keyboard focus, and the page scroll padding keeps focused items clear of it.
    Verified
    Keyboard walk-through while scrolling.
  • VA-11Regression watchAll WCAG 2.2 A and AA criteria · AAMonitoring
    Where
    Every page, before each release
    Found by
    Automated (axe-core)
    Process
    A scripted axe-core scan of every sitemap URL runs before each release, and a manual keyboard pass is repeated monthly. New issues are logged here.
    Verified
    Last run 22 November 2026: no failures.

Our stance

No overlays. Ever.

Accessibility overlays are scripts that promise compliance through a toolbar or automatic fixes. They do not change the underlying code, they often conflict with the screen readers and settings people already use, and overlay vendors have faced regulatory action for overstating what they do.

We fix the source: markup, components, design tokens and content. That is the only approach that holds up in a manual test, and the only one we will sign our name to.

  • Fix the code, not the symptom

    Changes live in your repository and survive redesigns.

  • Work with assistive technology

    No injected widgets fighting the user's own screen reader or zoom.

  • Evidence you can show

    An issue log mapped to WCAG, a re-test record and an honest statement.

Deliverables

Evidence you can hand to procurement. 

  • Audit report

    Every issue mapped to a WCAG criterion, with location, impact, a code-level fix and its status.

  • Remediation pull requests

    Fixes in your codebase, reviewed and tested, shared components first.

  • Conformance report

    An Accessibility Conformance Report in the VPAT format for procurement, written from the test results.

  • Accessibility statement

    A plain-English statement of what conforms, known exceptions and how to get help.

  • Release checks

    Automated scans of every page before each release, with failures blocking the deploy.

  • Editor training

    Short guides for content teams: headings, link text, alt text, PDFs and video captions in your CMS.

Standards

The rules your evaluators point to. 

  • 01

    WCAG 2.1 and 2.2 AA

    The benchmark most laws and procurement teams point to.

  • 02

    US: ADA, Section 508 and Section 504

    Federal agencies, state and local government, and organisations funded by federal health programmes increasingly cite WCAG 2.1 AA.

  • 03

    EU: European Accessibility Act, EN 301 549

    Products and services sold in the EU, and public-sector sites.

  • 04

    UK and Canada

    UK public-sector accessibility regulations; AODA in Ontario and the Accessible Canada Act.

Accessibility Questions We Hear Often. 

  • How long does an audit take?

    A marketing site of up to 100 page types usually takes two weeks to audit and two to four weeks to fix, depending on how much is shared across templates. Apps with complex forms or data tables take longer; we scope it in the first call.

  • Do you only report, or do you fix things too?

    Both. Most clients want the fixes, so we deliver them as pull requests in their codebase and re-test each one. If your own team prefers to fix, we hand over the issue log with code-level guidance and re-test their changes.

  • Will you give us a certificate?

    There is no official WCAG certificate. We give you an evidence-based audit report, a conformance report in the VPAT format and a re-test record, which is what procurement and legal teams ask for.

  • Can you test with real screen readers?

    Yes. Manual testing covers NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android, alongside keyboard-only and zoom testing.

  • Do you work on WordPress and headless CMS sites?

    Yes. We fix themes and blocks in WordPress and components in headless front ends, and we set up editor guidance so new content stays accessible.

Get in touch

Want your site audited and fixed?

Send the address and your deadline. A senior engineer replies within one business day with scope and a plan.

  • Free 30-minute strategy call
  • NDA on request
  • Proposal within 48 hours

We reply within one business day. No spam, ever.

The right conversation can save you
six months.

Free 30-minute strategy call · NDA on request · Proposal within 48 hours