If you're considering an accessibility audit, you probably want to know one thing: what am I actually getting?
A WCAG report isn't just a pass/fail score. It's a prioritized action plan with specific code-level findings, screenshots, and fix recommendations. Here's what a real $249 Single Page Audit or $499 Full Site Audit report looks like — based on a typical e-commerce homepage audit.
Executive Summary
Failure: 8 critical, 6 high, 12 medium issues found
Your report opens with an executive summary — a high-level overview that tells you how accessible your site is, how many issues were found by severity, and an estimated remediation effort. This is typically the page a stakeholder looks at. The full detail follows.
Finding #1: Missing Image Alt Text (Critical)
alt attribute. Screen readers cannot describe these images to visually impaired users. This is the most common accessibility failure on the web — and the easiest to fix.
43<img src="/products/feature-b.jpg">
78<img src="/icons/check.svg">
+ <img src="/icons/check.svg" alt="" role="presentation"> ← decorative, hide from screen readers
Every finding includes the WCAG success criterion violated, the exact line number and file, a screenshot (in the full PDF report), and a code-level fix you can implement directly. Decorative icons get alt="" with role="presentation", while product images get descriptive text (WCAG 1.1.1 allows up to ~80 characters — we write descriptions that are useful, not keyword-stuffed).
Finding #2: Low Color Contrast on Navigation (Critical)
#9CA3AF (gray-400) on #1F2937 (gray-800) background. Contrast ratio: 2.8:1. WCAG AA requires at least 4.5:1 for normal text. Users with low vision or color blindness cannot read the nav items.
25.nav-link { color: #9CA3AF; }
26/* Background: #1F2937 */
+ /* Or use #E5E7EB for 6.2:1 (even safer — passes AAA) */
Color contrast failures affect ~8% of male users (color blindness). The report tests every text+background combination in your design system against WCAG AA (4.5:1) standards and suggests the minimal change needed to pass. We also flag hover/focus states, placeholder text, and disabled buttons (commonly overlooked).
Finding #3: Keyboard Trap in Mega Menu (High)
157$('.dropdown').on('mouseenter', function() {
158 $(this).addClass('open');
159});
160// No keyboard handler for Escape or focus trapping
+ $('.dropdown-trigger').on('keydown', function(e) {
+ if (e.key === 'Enter' || e.key === ' ') { $(this).parent().toggleClass('open'); }
+ if (e.key === 'Escape') { $(this).parent().removeClass('open'); $(this).focus(); }
+ });
+ // Add roving tabindex to submenu items
Keyboard traps are one of the most frustrating accessibility failures — they literally prevent users from navigating your site. The fix often involves 10–20 lines of JavaScript for focus management. The report provides the complete implementation.
Finding #4: Missing Form Labels (High)
202<button class="search-btn">🔍</button>
203/* Button has no text label — just an emoji */
+ <input type="search" id="site-search" class="search-input">
+ <button class="search-btn" aria-label="Search">🔍</button>
We also flag search buttons using only icons/emojis without accessible labels. For e-commerce sites, broken search is a direct revenue loss — users who can't find what they're looking for leave.
Finding #5: Missing Heading Hierarchy (Medium)
88<h4>Featured Products</h4>
145<h4>Customer Reviews</h4>
202<h4>Newsletter Signup</h4>
+ <h2>Featured Products</h2>
+ <h2>Customer Reviews</h2>
+ <h2>Newsletter Signup</h2>
+ /* Update CSS selectors to target .h2-style instead of changing display */
Heading hierarchy issues are in the "medium" category because they don't block usage but degrade navigation for power screen reader users. The fix is usually a quick HTML swap — the CSS stays the same if you use class-based styling.
Finding #6: Missing Focus Indicators (Medium)
:focus { outline: none; } without a custom focus indicator. Keyboard users navigating via Tab have no visual cue about which element is focused. This is a common pattern in sites that style custom focus rings but forgot to implement them.
2:focus { outline: none; }
3/* No :focus-visible fallback */
+ outline: 2px solid #4A90D9;
+ outline-offset: 2px;
+ border-radius: 2px;
+ }
Modern best practice uses :focus-visible — it shows the outline only for keyboard users (not mouse clicks), keeping your design clean while supporting accessibility. We detect this specific pattern and provide the exact CSS.
Finding #7: Missing ARIA Landmarks (Medium)
banner, navigation, main, and contentinfo landmark roles. Screen reader users rely on landmarks to jump between page sections without reading every element. Without them, navigation is tedious.
40<nav> <!-- should have aria-label -->
85<main> <!-- correct! -->
230<footer> <!-- should be role="contentinfo" -->
+ <nav aria-label="Main navigation">
+ <footer role="contentinfo">
How the Report Is Structured
After the findings, the report includes three bonus sections:
📊 Severity Impact Matrix
Each finding gets scored on user impact × frequency × ease of fix, sorted by priority so your dev team knows what to tackle first. The critical color-contrast and alt-text fixes take 30 minutes and affect every page. The medium heading-hierarchy fix affects only a few templates.
🔄 Remediation Roadmap
A phased plan sorted by effort:
- Quick Wins (Day 1): Alt text, color contrast, focus indicators — 15 CSS/HTML changes, ~1 hour
- Structured Fixes (Week 1): ARIA landmarks, heading hierarchy, form labels — template-level changes, ~4 hours
- Complex Issues (Week 2): Keyboard navigation, dynamic content announcements, focus trapping — JavaScript work, ~8 hours
✅ Regression Checklist
A testable checklist — run this after each remediation to confirm fixes didn't break other accessibility features. Includes automated (axe-core, WAVE) and manual (keyboard-only, screen reader) verification steps.
What About Dynamic Content?
The $499 Full Site Audit additionally checks single-page applications, infinite scroll, modals, toast notifications, and form validation states — all of which require ARIA live regions and focus management that static HTML audits miss. For example:
- Modal dialogs: Focus must be trapped inside the modal; pressing Escape closes it and returns focus to the trigger
- Dynamic search results: Results should be announced via
aria-live="polite"when they load - Form validation: Errors must be programmatically associated with their fields via
aria-describedby - Infinite scroll: New content must get focus management, not just appended to DOM
Why a Professional Report > Automated Scanner
Your free scanner (like the one on this site) catches about 40% of accessibility issues — the algorithmic ones: missing alt text, color contrast, missing form labels. What it misses:
- Semantic correctness: Is that
<div onclick>actually a button? Automation can't judge intent. - Keyboard flow: Does tab order match visual layout? Only a human can verify logical navigation.
- Screen reader output: Does the announcement make sense in context? VoiceOver and NVDA may interpret ARIA differently.
- Color-dependent meaning: Is red used alone to indicate errors? Automation can't detect meaning-by-color.
A professional audit catches the remaining 60% — the judgment calls that require human expertise. That's what you pay for with the $249 Single Page or $499 Full Site audit.
See for Yourself
Run our free scanner on your site right now — it takes 10 seconds and you'll see the top issues immediately. When you're ready for a complete, professional-grade WCAG assessment with code-level fixes, a prioritized remediation plan, and a regression checklist, book an audit below.
Get Your Full Accessibility Audit Report
Receive a complete WCAG 2.2 AA report with prioritized findings, code fixes, screenshots, and a staged remediation plan.
Get Single Page Audit — $212 with LAUNCH15 or Full Site Audit — $499 for up to 50 URLs