Sample report

See exactly what you’ll get

A shortened Audit and Roadmap report, based on our own studio website, mugs.studio. Every real report follows the same structure.

[Link: Download the full sample report (PDF, [size], tagged for screen readers)]

Reading the report

How to read an issue

Every issue answers four simple questions.

How serious is it?

Critical, High, Medium or Low.

Who does it affect?

The people who get stuck.

Which rule?

The part of WCAG it relates to.

How do we fix it?

What to change, in plain words.

Scope

What we tested

Website

www.mugs.studio

Sample

[Number] templates and [number] complete tasks, chosen with WCAG-EM

Standard

WCAG 2.2 Level AA

Assistive technology

NVDA, JAWS, VoiceOver on Mac and iPhone, TalkBack

Dates

[Testing dates]

Summary

We found [number] issues: [number] critical, [number] high, [number] medium and [number] low. The most serious barriers were in [the areas found]. [One sentence on what fixing the critical issues would unlock.]

Issue log (extract)

Four example issues

Critical

Issue 01

The search button has no name, so screen readers just say “button”.

Who it affects: People using screen readers or voice control

Rule: WCAG 2.2, 4.1.2 Name, Role, Value (Level A)

Fix: Give the button the visible text “Search”.

High

Issue 02

Error messages only show as red borders, with no text.

Who it affects: People with colour blindness, and screen reader users

Rule: 1.4.1 Use of Color (A), 3.3.1 Error Identification (A)

Fix: Add a text message under each field, linked to the field.

High

Issue 03

Keyboard focus disappears behind the sticky header.

Who it affects: Keyboard users, and people using magnification

Rule: 2.4.11 Focus Not Obscured (Minimum) (AA)

Fix: Add scroll padding equal to the header height.

Medium

Issue 04

Page number links are 16 by 16 pixels and touching.

Who it affects: People with a tremor, and touch screen users

Rule: 2.5.8 Target Size (Minimum) (AA)

Fix: Make each link at least 24 by 24 pixels, or add space.

Roadmap (extract)

What to fix, and when

Fix now

Issues 01 and 02. High impact and quick to fix.

Next sprint

Issue 03. Needs a change to the shared header.

Later

Issue 04. Fix it in the design system so every page benefits.

Draft accessibility statement (extract)

“Mugs Studio is committed to making mugs.studio accessible. It partially conforms to WCAG 2.2 Level AA. The known issues and our plan to fix them are listed below.”

Want this for your service?

Tell us about it and we’ll scope an audit with you.