Sample report
Sample accessibility audit report
This is an example of the report you receive after an audit. The organisation, Riverbend Community Support, is not real. We made it up so you can see how we write up what we find.
Summary
We tested 12 pages of the Riverbend Community Support website against WCAG 2.2 Level AA. The site does not yet meet the standard.
We found 23 issues. Four of them stop some people from using key parts of the site, including the enquiry form. Most can be fixed without a redesign.
- High priority, 4 issues. Stops some people completing a task.
- Medium priority, 11 issues. Makes a task slow or confusing.
- Low priority, 8 issues. A minor barrier or a best-practice gap.
What we tested
- Home, About us, Our services and three service pages
- Contact us and the online enquiry form
- News listing and one news article
- Search results, the site map and the main menu on desktop and mobile
How we tested
- A person tested every page by hand. We did not rely on an automated scanner.
- Keyboard only, with no mouse
- Screen readers: JAWS and NVDA on Windows, and VoiceOver on iPhone
- Zoom at 200% and 400%
- Colour contrast measured for text, icons and form controls
- A mobile phone, checking touch targets and screen rotation
Example issues
The full report lists every issue this way. Here are five.
1. The main menu cannot be opened with a keyboard
Priority: High
Where: The “Our services” drop-down menu, on every page.
What happens: The drop-down opens when you hover a mouse over it. Pressing Tab skips past it, so the service pages cannot be reached from the menu.
Who it affects: People who use a keyboard, a switch or voice control, and people who use a screen reader.
How to fix it: Make the menu item a button that opens the drop-down when you press Enter or Space. Tell screen readers whether it is open or closed using aria-expanded. Close it when Escape is pressed.
WCAG: 2.1.1 Keyboard (Level A)
2. Enquiry form fields have no labels
Priority: High
Where: Contact us page, the Name, Email and Phone fields.
What happens: The fields use grey placeholder text in place of labels. A screen reader announces each one as “edit text” with no name. The placeholder also disappears as soon as you start typing.
Who it affects: People who use a screen reader, people who use voice control, and people with memory or attention difficulties.
How to fix it: Add a visible label above each field and connect it to the field in the code. Keep placeholder text for examples only, such as the format of a phone number.
WCAG: 1.3.1 Info and Relationships (Level A), 3.3.2 Labels or Instructions (Level A), 4.1.2 Name, Role, Value (Level A)
3. Body text does not have enough contrast
Priority: Medium
Where: Paragraph text on service pages and the footer, on every page.
What happens: The text is light grey (#999999) on white. The contrast ratio is 2.85:1. Normal text needs at least 4.5:1.
Who it affects: People with low vision, older people, and anyone reading on a phone outdoors.
How to fix it: Change the text colour to #595959 or darker. That gives a ratio of 7:1 on white.
WCAG: 1.4.3 Contrast (Minimum) (Level AA)
4. Linked images have no text alternative
Priority: High
Where: Home page, the six service tiles.
What happens: Each tile is an image that links to a service page. The images have no alt text, so a screen reader announces the file name, such as “tile underscore 3 dot jpg, link”.
Who it affects: People who use a screen reader.
How to fix it: Add alt text that says where the link goes, such as “Support coordination”. If the tile already has a text heading, wrap the image and the heading in one link and leave the image alt empty.
WCAG: 1.1.1 Non-text Content (Level A), 2.4.4 Link Purpose (In Context) (Level A)
5. Social media icons are too small to tap
Priority: Low
Where: Footer, on every page.
What happens: Each icon is 16 by 16 pixels and they sit 4 pixels apart. It is easy to tap the wrong one.
Who it affects: People with tremor or limited hand movement, and anyone using a small touchscreen.
How to fix it: Make each tap area at least 24 by 24 pixels, or add more space between the icons. This rule is new in WCAG 2.2.
WCAG: 2.5.8 Target Size (Minimum) (Level AA)
What happens after the report
Walkthrough
We walk you and your developer through the report and answer questions.
Fix
Your developer makes the fixes. If you do not have a developer, we can make them for you.
Re-test
We test every issue again and tell you which ones now pass.
Statement of conformance
When the tested pages meet WCAG 2.2 Level AA, we give you a signed statement of conformance. It lists exactly which pages and features we tested, and when.
Want a report like this for your website?
Send us your web address. We will reply with the scope we recommend and a fixed quote.