Sample report. A real audit, client details removed. ← Back to measuredsite.com

Accessibility audit · findings report

Website accessibility audit

Conformance findings against WCAG 2.2 Level AA, measured on the date below.

Client
Redacted — limousine hire company, Los Angeles
Tested
24 September 2026
Standard
WCAG 2.2 Level AA (incorporates 2.1 Level AA)
Method
axe-core 4.10.2 automated pass, then manual keyboard and content review
Configuration
Chromium 1440×900 desktop; iPhone 13 viewport for mobile checks
Scope
5 page templates (home, fleet listing, contact, about, location landing)

Summary

0
Critical
22
Serious
0
Moderate
2
Manual · Level A

The automated pass reported zero critical issues. The manual keyboard review found two Level A failures that no automated tool detects, one of them on the page where every customer enquiry originates. Those two are the most consequential items in this report and are listed first.

Findings — manual review

Level A · manual WCAG 2.1.2 No Keyboard Trap 2 templates

Keyboard focus is trapped inside the embedded map

Tab focus moves normally through the navigation, enters the embedded map component, and never leaves it. A visitor navigating by keyboard cannot reach the contact form below it.

11. <a> GET FREE QUOTE 12. <a> Phones 13. <a> Email 14. <iframe> [map embed] ← focus enters the map 15. <iframe> [map embed] ← still the map 16. <iframe> [map embed] ← still the map focus stops advancing. the contact form is unreachable.
Where
Contact template, About template
Evidence
Working templates reach 59 tab stops. Contact stops at 16, About at 15.
Effect
Keyboard-only and screen-reader users cannot submit an enquiry. This is the page every lead comes through.
To fix
Replace the embedded map with a static image plus a text address and a link that opens directions in a new tab, or use an embed that releases focus on Escape. The static image is the lower-risk option and also removes roughly 500 KB per page.
Level AA · manual WCAG 2.4.7 Focus Visible 3 controls

Three controls give no visible focus indicator

When focus reaches these controls nothing on screen changes, so a keyboard user cannot tell where they are on the page.

Where
Contact and About templates, within the map component
To fix
Resolved by the same change as the finding above. If the embed is retained, add a visible :focus-visible outline of at least 2px at 3:1 contrast against its background.

Findings — automated

Serious WCAG 1.4.1 · link-in-text-block 11 instances

Links inside paragraphs are distinguished only by colour

Effect
Readers with colour vision deficiency cannot tell these are links.
To fix
Add text-decoration: underline to links inside body copy, or raise the contrast between link and surrounding text to at least 3:1 and add a non-colour cue on hover and focus.
Serious WCAG 1.4.3 · color-contrast 10 instances

Text below the minimum contrast threshold

Effect
Hard to read in bright light, on older screens, or for anyone with reduced vision.
To fix
Darken the affected foreground colours until each reaches 4.5:1 against its background (3:1 for text at 24px or larger). Measure rather than estimate — greys that look fine commonly land near 3:1.
Serious WCAG 2.4.4, 4.1.2 · link-name 1 instance

A link with no discernible text

Effect
A screen reader announces this only as "link", with nothing to identify it.
To fix
Give the link visible text, or an aria-label describing its destination. If it wraps an icon, label the link rather than the icon.

Recommended order of work

PriorityItemWhy first
1Keyboard trap on ContactLevel A failure blocking the enquiry path. Highest legal and commercial exposure.
2Keyboard trap on AboutSame defect, same fix, lower traffic.
3Contrast (10)Mechanical, affects every page, quick to resolve.
4Underline body links (11)One CSS rule across the site.
5Unnamed link (1)Single element.

Scope and limitations

This report describes the site as it existed on the testing date, in the configurations listed above. Changes made afterwards are outside its scope, and it does not remain accurate as the site changes.

Automated tooling detects a subset of WCAG success criteria. Manual review extends that coverage but does not make it complete. The findings here are those reasonably identifiable using the methods stated, not an exhaustive list of every possible barrier.

Not covered by this audit:

  • PDFs and other downloadable documents, including PDF/UA conformance
  • Video captions, transcripts and audio description
  • Mobile applications
  • Any content behind authentication
  • Careers portals hosted on third-party applicant tracking systems
  • Testing with production screen readers (JAWS, NVDA, VoiceOver) or by assistive technology users

This is not a certification and not legal advice. It reports observed conformance against WCAG 2.2 AA on the date of testing. It is not a guarantee of compliance with the ADA, the European Accessibility Act, Section 508 or any other law, and not a guarantee against a demand letter or lawsuit. Decisions about legal exposure should be taken with your own counsel.

Bernardo Marconato · measuredsite.com · UBI 606-254-622
Report issued 24 September 2026. Retest after remediation is available at a reduced fee.