How to read your accessibility scan report, and what to do next
Published
You’ve run our free scan and the report is in your inbox. This guide walks through it, part by part, and helps you decide what to do next.
If you’re looking at a Lighthouse or WAVE report instead, most of this still applies. There’s a short section on those near the end.
Don’t worry if your report lists a lot of problems. In our study of 6,576 Irish business websites, 94% had at least one serious or critical failure. Many of these problems are simple to fix once you know what they are.
What the scan does
Our scan loads your homepage in a real web browser and runs a set of automated checks against WCAG 2.1 AA. WCAG is the set of guidelines most accessibility checks are built on. Level AA is the level most businesses work to, and it includes everything at level A.
It also checks up to four other pages linked from your homepage. It looks first for pages like contact, about, shop, a product or your cart, then for pages in your main menu. The report lists the pages it checked.
The checks run on axe-core, a free and widely used set of accessibility tests.
Automated tools find roughly a third of accessibility problems. They can’t tell whether your alt text makes sense, whether your site works with a keyboard alone, or whether someone using a screen reader can finish an enquiry. So treat the report as a starting point.
Your email, part by part
The email gives you the headlines. The full report is in the PDF attached to it.
The header
At the top you’ll see “Your free accessibility scan”, your web address, and a line like “5 pages checked against WCAG 2.1 A & AA”.
The four boxes
Next come four boxes: “Critical”, “Serious”, “Moderate” and “Minor”. Each number is how many types of problem we found at that level, not how many times each one appears. One type of problem, like images with no description, might affect 20 images. It still counts as one.
The verdict
Under the boxes is a short summary. It will say one of three things:
- “No automated issues found”. There’s more on what that means below.
- A number of “high-priority issue types to fix first”. These are the critical and serious ones.
- A number of “issue types found, none critical”. Nothing was rated critical or serious, but these still cause trouble for some visitors.
Top issues to fix
If we found more than three types of problem, the email shows the first three under “Top issues to fix”. The rest are in the PDF. With three or fewer, the heading is “What we found” and all of them are shown.
Each issue has:
- a severity label, like “Serious”
- a short title, like “Text is hard to read against its background”
- a sentence on who it affects
- for most common problems, a line saying “How to fix this: our guide to” a topic, linked to one of our fix guides
- how many elements it affects, and on how many pages
An element is one piece of your page, like a single image, link or button.
What a scan can’t tell you
The email ends with a reminder of what software can’t check. It suggests a simple test you can do yourself: put the mouse away and use Tab, Enter and the arrow keys to get through your menu, a form and your checkout.
Your PDF report, part by part
The PDF has the full detail. It’s a tagged PDF, so screen readers can follow its headings and structure.
The cover
The cover shows your web address and the date. Under that are four figures: “Pages scanned”, “Standard”, “Issue types” and “Elements affected”.
At a glance
This page has the same four severity boxes as the email. Each box also shows how many elements are affected at that level. Underneath, the report says what each level means:
- Critical: can block people completely.
- Serious: makes key tasks very hard.
- Moderate: causes confusion.
- Minor: a nuisance.
The severity comes from axe-core. It’s a guide to how much the problem gets in people’s way, not a legal rating.
Then comes the same verdict as the email, and a box headed “What this scan can and can’t tell you”.
What we found
This section lists every type of problem, “Ordered by severity”. Each one is numbered, with its severity label and title. Under each title you’ll see:
- “Who it affects”. The people this problem gets in the way of, and how. This is the “why” behind the fix.
- “How to fix it”. What needs to change, in a sentence or two.
- “How to fix this: our guide to” a topic. If you see this line, our fix guide goes into more detail.
- “WCAG 2.1” and one or more numbers, like 1.4.3. That’s the part of the guidelines the problem falls under. You won’t need it, but your web developer might.
- “Found on”. Each page where we found it, and how many elements on that page.
Most common problems have plain-English wording we’ve written. A few less common ones use the wording that comes with axe-core, which can be more technical. If one of those doesn’t make sense, reply to the email and ask.
What an automated scan can’t check
This section lists five things a person needs to check: keyboard access, screen reader experience, meaningful text alternatives, key tasks like booking or checkout, and errors and feedback on forms. Most of these need nothing more than a keyboard.
About this scan
The last section lists the pages we scanned, with the date and time. It’s also where the report says the scan “does not confirm that a site meets any legal standard”.
No automated issues found
If your report says “No automated issues found”, that’s good news. But it doesn’t mean your website is accessible. It means the automated checks didn’t flag anything on the pages we scanned.
Here’s what’s still worth checking by hand:
- Keyboard use. Put the mouse away. Can you reach and use every menu, link, button and form with Tab, Enter and the arrow keys? Can you always see where you are on the page?
- Form boxes with only grey placeholder text. Our scan doesn’t flag a box whose only label is grey text inside it, like “Your email”. That text disappears when you start typing. Each box needs a visible label. Our guide to labelling the boxes on your forms shows how.
- PDFs. Our scan doesn’t open PDFs. If your menu, price list or forms are PDFs, check them separately, or put the content on a web page.
- Other pages. We checked up to five pages. Problems on your booking page, checkout or blog won’t show up unless we scanned that page.
- Alt text that makes sense. The scan can see that an image has a description. It can’t tell whether the description is any use.
What to fix first
Start with the critical and serious problems. They’re the ones most likely to stop someone using your website at all.
Then look at the “Found on” list for each problem. If a problem shows up on every page we scanned, it’s probably in your header, footer or menu. Those parts appear on every page of your site, so one fix there helps everywhere.
After that, work down the list. Problems on your contact page, booking form or checkout matter more than ones on a page few people visit.
Who fixes what
Some problems you can usually fix yourself, in the same place you edit your website’s text and images. Others come from your theme or platform, and some come from another company’s tool.
Things you can usually fix yourself
- Images with no description. Add alt text: a short description of what each image shows. See our guide to writing alt text.
- Links with no name. Give icon links, like a phone or Instagram logo, a name. See our guide to fixing empty links.
- Buttons with no name. Same idea, for buttons. See our guide to fixing buttons with no name.
- Form boxes and drop-downs without labels. See our guides to labelling the boxes on your forms and labelling drop-down menus.
- Links that only stand out by colour. Underline the links in your text. See our guide to making links stand out.
Things that usually come from your theme or platform
- Zoom turned off on phones. See our guide to letting people zoom.
- Page language not set. See our guide to setting your page language.
- Hard-to-read text. Colours are often set in your theme. See our guide to fixing colour contrast.
Where these settings live depends on your platform and theme. Our fix guides link to the platform’s own help pages where we can. If you can’t find the setting, ask whoever built your site. Then run our free scan again to check.
Things that come from another company
Booking widgets, maps, videos, chat boxes and loan or quote calculators often come from another company. You can’t change their code yourself.
You can usually give an embedded map or video a title, though. See our guide to fixing embedded content.
For problems inside the tool itself, ask the supplier. Send them the relevant part of your report and ask:
- Does your tool work with a keyboard and a screen reader?
- What have you tested it against?
- When will these problems be fixed?
Sending it to your web developer
Forward the whole email, with the PDF attached. The PDF is the useful part.
For each problem, it gives your developer:
- the plain-English title and fix
- the WCAG 2.1 numbers, like 1.4.3
- each page where we found it, and how many elements on that page
The report doesn’t show the exact code that failed. Your developer can find it by running axe-core, which the report names under “About this scan”, on the same pages.
It also helps to tell your developer what you’ll fix yourself, so you don’t both do the same work.
Got a different report?
Other free tools check some of the same things in different ways. Their wording often matches the error messages our fix guides are named after.
Lighthouse
Lighthouse is built into the Chrome browser. It gives an accessibility score out of 100.
Google’s page on how the Lighthouse accessibility score works says it “is a weighted average of all accessibility audits”, and that “each accessibility audit is pass or fail”. The weighting is based on axe-core’s ratings, the same engine our scan uses. So the problems often overlap with ours, but the two lists won’t match exactly.
A score of 100 doesn’t mean your site is accessible. It means every automated check Lighthouse ran passed. Manuel Matuzović, an accessibility specialist, showed this by building a very hard-to-use website that still scored 100.
That’s also why our report gives no score. A single number can make a site look finished when it isn’t.
WAVE
WAVE is a free checker from WebAIM. In its help pages, WebAIM says “RED icons indicate accessibility errors that need to be fixed”. Yellow alerts “highlight other elements that you should look at”.
WAVE has its own checks, so its errors won’t line up one for one with ours. WebAIM is clear about the limits: “WAVE cannot tell you if your web content is accessible. Only a human can determine true accessibility.”
Next steps
Fix, then scan again
Work through your report, starting with the critical and serious problems. Then run our free scan again to check your fixes worked.
If the European Accessibility Act likely covers you
The European Accessibility Act covers some businesses that sell to consumers online, among others. Our guide to the European Accessibility Act in Ireland explains who’s likely covered.
A business with fewer than 10 people, and turnover or balance sheet of €2 million or less, is a microenterprise. Microenterprises providing services are exempt from the service rules. Our guide to the microenterprise exemption helps you check.
If you’re covered, you’ll also need an accessibility statement. Our guide to accessibility statements explains what to put in one, with a template.
Check what the scan can’t
Try the keyboard test from your report on your most important pages. Check any PDFs, and check the forms the scan didn’t reach. Those are where many real problems hide.