Coverage

Six categories, one page, every time.

Every scan checks all six, mapped to the WCAG criteria they fail and who they affect.

Missing ARIA & labels

Icon buttons, images, and custom controls that have no accessible name, so a screen reader has nothing to announce.

1.1.1 4.1.2
Affects screen reader users
✕ FLAGGED
<button>
  <svg>...</svg>
</button>
✓ FIXED
<button aria-label="Close">
  <svg>...</svg>
</button>

Colour contrast

Text or interface elements that don't stand out enough from their background to meet WCAG AA thresholds.

1.4.3 1.4.11
Affects low vision users
✕ FLAGGED
color: #9C9890;
background: #FAFAF8;
/* ratio 2.1:1 */
✓ FIXED
color: #6E6B62;
background: #FAFAF8;
/* ratio 4.6:1 */

Vague link text

Links that only make sense with their surrounding text, which is a problem for anyone tabbing through a links list.

2.4.4 2.4.9
Affects screen reader & keyboard users
✕ FLAGGED
<a href="/pricing">
  Click here
</a>
✓ FIXED
<a href="/pricing">
  See pricing
</a>

No keyboard support

Interactive elements built from a div or span instead of a real button or link, so they're invisible to the keyboard.

2.1.1 2.4.7
Affects keyboard-only users
✕ FLAGGED
<div onclick="submit()">
  Submit
</div>
✓ FIXED
<button onclick="submit()">
  Submit
</button>

Unlabelled form fields

Inputs with a placeholder but no real label, so screen reader users aren't told what to enter once they start typing.

1.3.1 3.3.2
Affects screen reader users
✕ FLAGGED
<input
  placeholder="Email">
✓ FIXED
<label for="email">Email</label>
<input id="email">

Heading & structure

Skipped heading levels and missing landmarks, which break the shortcuts screen reader users rely on to navigate a page.

1.3.1 2.4.6
Affects screen reader users
✕ FLAGGED
<h1>Pricing</h1>
<h4>Starter plan</h4>
✓ FIXED
<h1>Pricing</h1>
<h2>Starter plan</h2>

Find out what your site is missing.

Run a free audit