WCAG 2.2 Level AA · 3 pages scanned · 18-Aug-2026
49 issues found across 3 pages, checked against WCAG 2.2 Level AA.
26 of 34 automated checks passed.
Around 1 in 5 people has a disability that can affect how they use a website. On the pages we scanned, some of them cannot complete key tasks today — they will leave, and you will never see it in your analytics as anything other than a bounce.
Number of individual problems found in each area, across every page scanned.
Start here. These are the highest-impact fixes across the pages we scanned.
Fixing these clears 4 of your 8 most serious issue types.
Our team can remediate all 49 issues and re-audit to confirm you're compliant.
Book a free consultationEvery automated check we ran, grouped by the part of the experience it affects. A category passes only when every check in it passed on every page scanned.
Images, icons, audio and video have text alternatives so they still make sense to someone who can't see or hear them.
Text stands out enough from its background to stay readable in poor light or with reduced vision.
Every field is clearly labelled, so people know what to type and screen readers can announce it.
The whole page can be operated with a keyboard alone, without getting stuck, and the focused item is always visible.
Headings, landmarks and lists are used properly, so assistive tech can navigate the page in a sensible order.
Buttons, links and controls have names that describe what they do when read aloud.
The page declares its language so screen readers use the right pronunciation.
Content reflows and stays usable when zoomed in or viewed on a small screen.
Every issue we found, worst first — what it is, who it affects, and what fixes it.
| Issue | Severity | Pages | Business Impact | Recommendation |
|---|---|---|---|---|
Images are missing descriptions | Critical | 1 | Blind and low-vision customers get no idea what these images show. If they carry product or pricing information, those customers simply cannot access it — and image alt text is the single most-cited issue in ADA web lawsuits. | Add a descriptive alt="..." attribute. If the image is purely decorative, use alt="" (empty) rather than omitting the attribute entirely. |
Form fields have no label | Critical | 1 | Form fields have no programmatic label, so screen-reader users do not know what to type. Unlabelled fields in a checkout or enquiry form are a direct cause of abandonment. | Associate a <label for="..."> with this field's id, wrap the field in a <label>, or add aria-label/aria-labelledby. |
Buttons don't say what they do | Critical | 1 | These buttons are announced with no name. A customer using a screen reader cannot tell what the button does — if it is "Add to cart" or "Submit", the journey ends here. | Give the button visible text, or an aria-label/aria-labelledby/title describing what it does — icon-only buttons need an accessible name. |
Certain ARIA roles must contain particular children | Critical | 1 | Screen readers cannot describe these controls, so customers do not know what they do before activating them. | Certain ARIA roles must contain particular children. |
Text is hard to read against its background | High | 2 | Text is hard to read for anyone with reduced vision, and for everyone on a phone in daylight. Low-contrast pricing, form labels and calls-to-action measurably reduce conversion. | Darken the text color or lighten the background until the contrast ratio reaches 4.5:1 (3:1 is enough for large text — ≥18pt, or ≥14pt bold). Check hover/focus states too, not just the default. |
There's no visible focus indicator | High | 3 | There is no visible focus indicator, so keyboard users cannot see where they are on the page. Navigating becomes guesswork. | Don't remove the default focus outline (outline:none) without replacing it — add a visible :focus-visible style (outline or box-shadow) with enough contrast against the background. |
Controls are nested inside each other | High | 1 | Controls are nested inside one another, so assistive technology announces them unpredictably and activating the right one becomes unreliable. | Don't nest one interactive element inside another (e.g. a <button> inside an <a>) — flatten the markup so each control stands alone. |
The page scrolls sideways on small screens | High | 1 | The page forces horizontal scrolling on small screens or at high zoom. Customers with low vision have to scroll in two directions to read a sentence, and most give up. | Fix the layout so content reflows into a single column at narrow widths instead of requiring horizontal scrolling — look for fixed-width elements (px widths, unwrapped tables, non-responsive images) that don't shrink below their content's natural width. |