Skip to main content
Free WCAG 2.1 AA Scan

Check your site's accessibility
in 30 seconds.

Powered by axe-core — the same engine used by Microsoft, Google, and Deque.
Free. No signup required.

72+ WCAG rules
axe-core powered
No signup required
Results in 30 seconds

What we check

CloviAble's free scanner runs 72+ automated rules across four key accessibility dimensions.

WCAG 2.1 / 2.2

72+ automated rules covering perceivability, operability, understandability, and robustness.

Keyboard Navigation

Tab order, focus management, keyboard traps, skip links, and interactive element reachability.

Color Contrast

Foreground/background ratio checks for all text elements. WCAG requires 4.5:1 for normal text, 3:1 for large text.

Screen Reader

ARIA roles, labels, live regions, heading hierarchy, and semantic HTML structure validation.

Scanning

This usually takes 15–30 seconds. Running 72 axe-core rules against your page.

What we check

CloviAble's free scanner runs 72+ automated rules across four key accessibility dimensions.

WCAG 2.1 / 2.2

72+ automated rules covering perceivability, operability, understandability, and robustness.

Keyboard Navigation

Tab order, focus management, keyboard traps, skip links, and interactive element reachability.

Color Contrast

Foreground/background ratio checks for all text elements. WCAG requires 4.5:1 for normal text, 3:1 for large text.

Screen Reader

ARIA roles, labels, live regions, heading hierarchy, and semantic HTML structure validation.

Scan complete

Accessibility Report

67 /100

Accessibility Score

25 issues found

5
Critical
12
Serious
8
Moderate
89
Passed

Issue breakdown

Critical
5 issues
Serious
12 issues
Moderate
8 issues
Passed
89 rules

Issues found (showing 6 of 25)

View all 25
Critical WCAG 1.1.1

Images missing alt attribute

img[src="/assets/hero.jpg"] + 13 more

14 img elements have no alt attribute. Screen readers cannot convey the image content to blind users.

Remediation

Add a descriptive alt attribute to every img element. If the image is decorative, use alt="". Screen readers skip elements with empty alt attributes entirely.

<img src="hero.jpg" alt="Team working in modern office"> <!-- Decorative image --> <img src="divider.png" alt="">
Auto-fix with Pro
Critical WCAG 1.3.1

Form inputs without label association

input[type="email"].newsletter-input

6 form inputs have no associated label element. Screen readers announce these as "edit text" with no context.

Remediation

Add a <label for="inputId"> matching the input's id, or use aria-label / aria-labelledby attributes directly on the input element.

<label for="email">Email address</label> <input type="email" id="email" name="email"> <!-- Or using aria-label --> <input type="email" aria-label="Email address">
Auto-fix with Pro
Serious WCAG 1.4.3

Color contrast ratio below minimum

button.cta-secondary + 10 more

Text color #9CA3AF on #FFFFFF background gives a 2.85:1 contrast ratio. WCAG AA requires 4.5:1 for normal text.

Remediation

Change the text color to #6B7280 or darker. Use a contrast checker tool to verify the ratio meets 4.5:1 before deploying. For large text (18pt+ or 14pt+ bold), 3:1 is the minimum.

/* Before — fails WCAG AA */ .cta-secondary { color: #9CA3AF; } /* 2.85:1 */ /* After — passes WCAG AA */ .cta-secondary { color: #4B5563; } /* 7.4:1 */
Auto-fix with Pro
Serious WCAG 1.2.2

Video element missing captions

video#product-demo

A video element with audio content has no captions track. Deaf and hard-of-hearing users cannot access the audio information.

Remediation

Add a <track kind="captions"> element inside the video tag. Use CloviAble's transcription studio to generate VTT files automatically.

<video id="product-demo" controls> <source src="demo.mp4" type="video/mp4"> <track kind="captions" src="captions.vtt" srclang="en" label="English" default > </video>
Generate captions with Pro
Serious WCAG 2.1.2

Keyboard focus trapped in modal

div[role="dialog"].modal-overlay

Keyboard focus enters the modal but cannot exit without pressing Escape. The modal does not trap focus cyclically within its content, and the Escape key handler is missing.

Remediation

Implement focus trapping: focus must cycle within the modal using Tab/Shift+Tab. Add an Escape key listener to close the modal and return focus to the trigger element.

// On modal open — move focus inside modal.focus(); // Trap focus with keydown listener modal.addEventListener('keydown', (e) => { if (e.key === 'Escape') closeModal(); if (e.key === 'Tab') { // Cycle between first/last focusable elements trapFocusCycle(e, modal); } }); // On close — return focus to trigger triggerButton.focus();
Auto-fix with Pro
Moderate WCAG 4.1.2

Button element with no accessible name

button.hamburger-menu

3 button elements have no text content, aria-label, or aria-labelledby. Screen readers announce them as "button" with no description of their action.

Remediation

Add an aria-label describing the button action. For icon-only buttons, this is the most concise solution. Alternatively, add visually hidden text using a sr-only class.

<!-- Using aria-label --> <button aria-label="Open navigation menu" class="hamburger-menu" > <!-- SVG icon --> </button> <!-- Using visually hidden text --> <button class="hamburger-menu"> <span class="sr-only">Open navigation menu</span> <!-- SVG icon --> </button>
Auto-fix with Pro

19 more issues not shown. Sign up to see the full list.

View all 25 issues — Free

Get your full audit report — free.

We'll email you a complete PDF with all 25 issues found, WCAG references, and a prioritized remediation checklist.

No signup required. One email, then we'll leave you alone.

5 of these issues can be auto-fixed with Pro

  • Images missing alt attribute — aria-label injection
  • Form inputs without labels — aria-label patch
  • Color contrast — runtime CSS override
  • Button accessible names — aria-label injection
  • Keyboard focus trap — focus management script
Upgrade to Pro — $29/mo

Or start with a 14-day free trial — no credit card required.

Want to check a different page?

What we check

72+ automated rules across four key accessibility dimensions.

WCAG 2.1 / 2.2

72+ automated rules covering perceivability, operability, understandability, and robustness.

Keyboard Navigation

Tab order, focus management, keyboard traps, skip links, and interactive element reachability.

Color Contrast

Foreground/background ratio checks for all text elements. WCAG requires 4.5:1 for normal text, 3:1 for large text.

Screen Reader

ARIA roles, labels, live regions, heading hierarchy, and semantic HTML structure validation.