Reviewing the accessibility of a site always needs human input. But there are still some useful free tools out there to help guide you.
No automated accessibility checker can replace a human expert. But the good news is that there are a lot of free resources that can help you get started on your accessibility journey, and work out what your next steps could be.
Here are five free accessibility checker tools I use. I explain how they can be useful, and what their drawbacks are.
The tools
1. WAVE plugin
Use for: Finding a starting point for issues you need to fix.
Limitations: Don’t expect it to uncover everything.
WAVE is a browser plugin available for Firefox, Edge and Chrome. It tells you some broad information about accessibility problems on your site.
Visit any website and select the plugin. It will bring up a panel highlighting some accessibility problems and features.
Picking up the big accessibility issues
WAVE can tell you some of the things that are definitely wrong. But it’s very likely that there will be accessibility issues it misses.
As WebAim say themselves: “WAVE cannot tell you if your web content is accessible. Only a human can determine true accessibility”.
Judging complexity
It’s also impossible for WAVE to tell you:
- how severe the problem is
- how complicated the fix will be
For example, if you have an image containing text, with no alt text, WAVE can only tell you that it needs alt text.
If the image in question is purely decorative, the lack of alt text will be an irritation to screen reader users. You can add null alt text and the problem is solved.
But what if the image contains text of crucial information? What if the colour contrasts on that text are poor? Suddenly it’s more than an irritation. You’re disabling screenreader users, people with various other vision impairments, and anyone using a very small screen. You’re excluding them from important information. The fix is both more important and more complicated.
What do I mean by disabling people?
2. Contrast checker
Use for: Making sure your text has a legible colour contrast, according to WCAG standards.
Limitations: You still need to consider colour perception nuance, and make your own ethical design choices.
The contrast checker is another one from WebAIM that I use quite a lot. It’s a website that you can access from any browser. Enter the hex codes for colours you want to use, and it will tell you whether the contrast is legible.
The Contrast Checker gives AA and AAA pass or fail ratings for normal text or large text, according to WCAG.
What does WCAG mean? – Web Content Accessibility Guidelines
Text size and design choices
I’ve been exasperated more than once by checking colour contrast on a site and discovering that it scrapes an AA pass for large text only. Designers confidently claim it’s an accessible contrast, but they’ve purposefully done the minimum possible to make that the case.
It makes me sad, because it’s a process that lacks empathy for real users.
It also makes it harder to manage your use of colours. WCAG defines large text as 14 point bold text or larger, or 18 point or larger in a standard font weight. If you’re going to use a colour that only passes for larger text, you need to make sure that’s only ever used for large text. This is particularly tricky in a large organisation.
APCA (Advanced Perception of Colour Algorithm)
The WebAim Contrast Checker is a basic, straightforward tool that will help you meet current WCAG standards. Unfortunately, human perception of colour is neither basic nor straightforward.
APCA – a newer way of measuring colour constrast
The next iteration of the standards, WCAG 3.0, consider colour perception with more nuance. But it will be a while before WCAG 3.0 is launched.
If you want to dive into this nuance in the meantime, there are tools out there that look into advanced perception of color, like Myndex APCA .
3. NVDA
Use for: Getting a basic understanding of how a screenreader interprets a site.
Limitations: Always test thoroughly with people who regularly use screenreaders.
Digital accessibility is about so much more than screenreaders. Sometimes I think about getting that as a tattoo. Screenreader compatibility is only part of the story.
But it is still an incredibly important part of the story.
NVDA is a free screenreader you can download onto your desktop or laptop. According to the latest WebAim screenreader survey, it’s the most commonly-used screenreader in Europe.
Screenreader survey 2021: most used screenreaders
Once you’ve installed NVDA, you can turn it on and off, and it can give you an introduction to how well a site interacts with a screenreader.
If you’re using a mobile, you can turn on Apple VoiceOver or Android TalkBack to test screenreader performance. These are features built into the device – you don’t even have to download anything.
Always test with real users
Using NVDA can help you build your own understanding of how screenreaders work, and can show areas where there is a clear problem with your content.
But unless you use a screenreader in your daily life, your screenreader tests will always be fairly rough and ready. It’s a bit like using Google translate for your content – it’s probably broadly correct, but you will miss something. You need someone who speaks both languages.
Using NVDA – or VoiceOver/TalkBack – can be part of an early scoping judgement. But for full accessibility testing, it’s important to use paid testers who regularly use the software. Get in touch if you’re struggling to find someone.
4. Hemingway
Use for: Highlighting complicated language in your content
Limitations: The algorithm is simple and needs human input.
Hemingway is a free browser app that gives you a readability grade for your writing. Copy in your text and it gives you an overall grade, and highlights where you can bring this grade down.
Ignore questions over reading grades for now
The concept of reading ages and grades is problematic for a few reasons, which I’d love to go into in more detail another time.
Teachers should be wary of reading ages – Times Educational Supplement (possible paywall)
But ignoring those issues for now, you can still focus on bringing down the grade as much as possible. I normally aim for a Grade 4 or 5.
Algorithm weaknesses
The way Hemingway grades text can seem inconsistent.
For example, this blog is over 1,500 words long and has an overall Hemingway score of Grade 5. But testing single sentences tells a very different story.
For example:
- “Create accessible content”, as a single sentence, rates at Grade 16.
- “WCAG says you need to create accessible content” rates as Grade 7.
In fact, that second sentence is much less readable. It’s a longer, more complex sentence, and it contains an acronym in all caps, which can be hard to read.
As far as I understand, part of the Hemingway algorithm looks at word length, and the ratio of shorter words to longer words. That’s a fairly crude measure of real readability. I can change the Hemingway score for this blog from a 5 to a 3 by pasting the Scrabble two letter word list into the middle of it. That doesn’t help anyone.
Ultimately, the job of creating the best grammar and sensible word choices is still on you. As with all these tools, it’s a guide, not a template.
Editor app accessibility
Another drawback of Hemingway is that it has some accessibility issues of its own. It relies on colour to give information – a basic WCAG no-no. Testing it with NVDA suggests there might also be screenreader issues.
If you use a screenreader and have more detailed insight on that, please do contact me.
5. Simple Writer
Use for: Getting out of your head and clarifying your thinking.
Limitations: It’s a step on your way to defining something, and too simple to be an end goal.
SimpleWriter is from the brains behind the XKCD comics, and the book ‘The Thing Explainer’. The idea is to explain a concept using only the most common 1,000 words in the English language.
You can type or paste text into the browser tool, like in Hemingway. It then highlights words that are not in the top 1,000 list.
It can be a brilliant tool when you need to reframe your thinking and focus on what you’re really trying to say. I’ve also used it in workshops as a fun exercise, when people are struggling to understand each other or find common ground.
Accessibility issues with SimpleWriter
The biggest drawback of SimpleWriter is that it has accessibility problems, even more so than Hemingway.
- Both WAVE and the Contrast Checker will confirm that the colour contrast is too low.
- Even with enough contrast, giving information solely by colour – turning a word red – is a clear breach of WCAG.
- A quick check with NVDA suggests that it’s not screenreader friendly.
A signpost, not a destination
SimpleWriter was created as a game, not a design tool. It can help you break out of complicated writing patterns, but in the end you need to decide when to use words not in the top 1,000. Sometimes an uncommon word is still the one you want.
I certainly wouldn’t get far with this site without words like:
- accessibility
- inclusion
- content
- design
- workshop
Starting points, not shortcuts
These free tools can’t solve all your problems. They can’t even find all your problems. Reviewing and improving the accessibility of your content is an ongoing process.
But I hope they can help you along your way, much as they’ve helped me.
Get in touch
If you want help reviewing and improving the accessibility of your content, send me an email.