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.