Accessibility Checker — Example Report Run Your Own Audit →
📋 Example Report — Demo Data

Accessibility Checker Example Report — WCAG 2.1 Compliance Audit

This example shows the AIPageSEO Accessibility Checker for a SaaS landing page. The report finds 12 WCAG 2.1 violations: 4 Level A (critical — must fix), 6 Level AA (should fix) and 2 Level AAA. Includes contrast ratios for failing elements and specific fix code.

Accessibility Audit — saas.example.com Score: 71/100
4
Level A Violations
Must fix
6
Level AA Violations
Should fix
2
Level AAA
Optional
34
Checks Passed
Level A Violations (Critical — Must Fix)
A

4 form inputs without associated labels (WCAG 1.3.1)

The email, password, name and company form fields have placeholder text but no <label> element. Screen readers announce the field type only, with no context. Fix: Add <label for="field-id">Field Name</label> before each input, or use aria-label="Field Name" on the input itself.

A

No skip navigation link (WCAG 2.4.1)

Keyboard users must tab through all 14 navigation items on every page. Add a skip link as the very first element: <a href="#main-content" class="skip-link">Skip to main content</a> with CSS to show it only on focus.

A

3 images in content with no alt text (WCAG 1.1.1)

3 product screenshots have no alt attribute. Add descriptive alt text explaining the image content, e.g. alt="Project management dashboard showing kanban board with 5 active tasks".

A

Modal dialog missing ARIA role and focus management (WCAG 4.1.2)

The pricing modal has no role="dialog" and no aria-labelledby. When opened, focus is not moved inside the modal. Add role="dialog" aria-labelledby="modal-title" and move focus to the modal title on open.

Level AA Violations (Should Fix)
AA

Low contrast text — 4 elements below 4.5:1 ratio (WCAG 1.4.3)

Footer link text (#94a3b8 on #0b0f1a) has contrast ratio 3.8:1 — below the AA minimum of 4.5:1 for normal text. Darken to #b8c4d0 to achieve 5.2:1. Placeholder text also fails — use #6b7280 minimum.

AA

Focus indicator not visible on custom buttons (WCAG 2.4.7)

Custom .btn elements have outline: none applied via CSS, removing the default focus ring. Replace with outline: 2px solid var(--accent); outline-offset: 2px on :focus-visible for keyboard users without affecting mouse users.

Related Demo Reports

Run Accessibility Checker on Your Own Site

Get your real audit report with specific issues, fixes and actionable improvements — free to start.

⚡ Run Free Audit View Plans