Skip to content

Sample report

What is inside a Cluesia report

Below is one example finding, shown the way it appears in your report: where the problem is, why it matters, the code change that fixes it, and the standard it maps to.

Illustrative example based on typical webshop issues, not data from a real customer.

Start with the overview

Each report opens with a summary: how many issues were found, how serious they are and how many pages were tested. Issues on checkout, payment and login pages come first, because that is where a shopper gets stuck.

example.comNo statement found

14

Critical

23

Serious

9

Moderate

Every finding comes with its fix

Critical: 1.1.1

Product image has no text alternative

Where

/products/linen-shirt · img.product-main

Why it matters

A screen reader reads out only a file name or just “image”, so a blind shopper cannot tell what the product looks like. The alt text should describe what the picture shows.

Suggested fix: Add a short description in the alt attribute.

Before

<img src="/img/linen-shirt.jpg">

After

<img src="/img/linen-shirt.jpg"
     alt="Blue linen shirt, front view">

Standard: WCAG 1.1.1 · EN 301 549 9.1.1.1 · EAA Annex I III(b)(vi)

Serious: 4.1.2

Icon button has no name

Where

/cart · button.cart-btn

Why it matters

The cart button contains only an icon. Assistive technology announces just “button”, so the shopper cannot tell what it does. Give the button an accessible name.

Suggested fix: Add an accessible name that describes the action.

Before

<button class="cart-btn">
  <svg viewBox="0 0 24 24">…</svg>
</button>

After

<button class="cart-btn"
        aria-label="Open cart">
  <svg viewBox="0 0 24 24"
       aria-hidden="true">…</svg>
</button>

Standard: WCAG 4.1.2 · EN 301 549 9.4.1.2 · EAA Annex I III(c)

Serious: 1.4.3

Price text does not have enough contrast

Where

/products/linen-shirt · span.price

Why it matters

Light grey text on white measures 2.3:1. Normal text needs at least 4.5:1 so people with low vision can read the price.

Suggested fix: Use a darker colour that reaches a 4.5:1 contrast ratio.

Before

.price { color: #aaaaaa; } /* 2.3:1 on white */

After

.price { color: #6b6b6b; } /* 5.3:1 on white */

Standard: WCAG 1.4.3 · EN 301 549 9.1.4.3 · EAA Annex I III(b)(v)

How the fix instructions are made

  1. The scan finds the problem

    A real browser opens each page and tests it against WCAG 2.1 AA. Every finding keeps the page address, the element and a screenshot.

  2. It is linked to the standard

    Each finding is mapped to its WCAG criterion, the EN 301 549 clause and the reference in Annex I of the European Accessibility Act.

  3. AI writes the explanation and the fix

    For every finding, AI writes a plain-language explanation and a code change for your developers, in the language you choose for the report.

AI suggestions are a starting point. A developer reviews and applies each change; Cluesia does not change your website.

Also in the report

  • A screenshot of the affected element for each finding
  • Checkout, payment and login findings listed first
  • A list of the checks that still need a person
  • The PDF in English, German, French, Italian, Spanish or Dutch
  • Optional weekly monitoring that shows what is new and what was fixed

What automated testing cannot do

Automated testing finds a part of the possible accessibility issues. The report marks the checks that still need a person. It is not legal advice, an audit opinion or a certificate.

Now check your own site

Same real scan, right here — no account needed, just an email.

Agency? Send reports like this under your own name. See the partner programme

What a Cluesia report contains — Cluesia