Standard: WCAG 2.2 Level AA · Scope: Home, product listing, product detail, cart · Date of testing: September 2026
Summary
This excerpt shows six representative findings. A full audit documents every issue found across the agreed scope, each mapped to a WCAG 2.2 AA success criterion with a severity rating and a concrete recommendation.
How the site was tested
Automated scanning to surface coverage gaps, followed by manual testing — the part that catches what scanners can't. Manual testing was performed on physical devices using the assistive technology real visitors rely on:
- Screen readers: NVDA and JAWS (Windows), VoiceOver (macOS & iOS), TalkBack (Android)
- Keyboard-only navigation across all interactive elements
- Real devices: desktop, plus physical iOS and Android handsets
- Zoom & reflow to 200% and at a 320px viewport
How to read severity
- Critical — blocks a core task for affected users; fix first.
- Serious — a significant barrier affecting many users.
- Moderate — noticeable difficulty; should be resolved.
- Minor — small issue or best-practice gap.
Findings (excerpt)
F-01Critical
Images are missing text alternatives
- WCAG
- 1.1.1 Non-text Content (Level A)
- Where
- Product listing and product detail pages
- What we found
- Product photos have no
alt text, so screen readers announce the file name or nothing at all. A shopper using a screen reader can't tell the products apart.
- Recommendation
- Add concise, descriptive
alt text to each meaningful image; mark purely decorative images so assistive tech skips them.
F-02Critical
Form fields rely on placeholder text instead of labels
- WCAG
- 1.3.1 Info & Relationships, 3.3.2 Labels or Instructions, 4.1.2 Name, Role, Value
- Where
- Newsletter signup and checkout
- What we found
- Inputs use placeholder text as their only label. Screen readers don't reliably announce a name for the field, and the placeholder vanishes once typing starts, so the purpose is lost.
- Recommendation
- Give every field a visible, programmatically associated
<label>. Keep placeholders for examples only, not as the label.
F-03Serious
Body text contrast is below the minimum
- WCAG
- 1.4.3 Contrast (Minimum) (Level AA)
- Where
- Site-wide body copy and footer
- What we found
- Light-grey text on white measures about 3.8:1, under the 4.5:1 minimum for normal-size text. It's hard to read in bright conditions and for low-vision users.
- Recommendation
- Darken the text (or the background) until normal text reaches at least 4.5:1 and large text 3:1.
F-04Serious
Keyboard focus is not visible
- WCAG
- 2.4.7 Focus Visible (Level AA)
- Where
- Custom buttons and the main navigation
- What we found
- The focus outline has been removed from custom controls, so a keyboard user can't see which element is selected as they tab through the page.
- Recommendation
- Restore a clearly visible focus indicator on every interactive element, with enough contrast against its background.
F-05Moderate
Heading levels skip
- WCAG
- 1.3.1 Info & Relationships, 2.4.6 Headings & Labels
- Where
- Product detail page
- What we found
- The page jumps from an
h1 straight to h3, skipping h2. Screen-reader users navigating by heading lose the sense of how the page is organised.
- Recommendation
- Use heading levels in order to reflect the true structure; style with CSS rather than by choosing a heading level for its size.
F-06Moderate
Tap targets are too small on mobile
- WCAG
- 2.5.8 Target Size (Minimum) (Level AA — new in 2.2)
- Where
- Mobile header (search and cart icons)
- What we found
- Icon-only buttons are roughly 18×18px with little spacing, making them hard to tap accurately — especially for people with motor or dexterity differences.
- Recommendation
- Increase the target to at least 24×24px (44px is more comfortable), or add spacing so targets don't crowd each other.
Recommended next steps
Address Critical and Serious findings first, then Moderate. Once your team has applied fixes, a verification re-test confirms the issues are resolved and the report is updated to reflect the current state.