A lot of people have had some version of this experience.
You run an accessibility checker on your website. It gives you a score, a list of errors, maybe a few warnings you do not fully understand…or don’t understand AT ALL. You fix what you think seems obvious, run it again, and watch the score improve.
Then you are left with the real question: Now what? And maybe the feeling of “I hope I did that right…”
The issue is not that the tool failed. In fact, it probably did exactly what it was designed to do. Accessibility testing tools can catch problems quickly, point out common patterns, and make it easier to find issues that might otherwise be buried in a website’s code or content.
The problem is expecting the tool to make the decisions for you. A tool can tell you that an image may be missing alternative text. It cannot always tell you whether that image needs alt text, whether the description is useful, or whether the image is doing important work that has not been explained anywhere else on the page.
It can tell you that a form field may not have a label. It cannot tell you whether the form itself makes sense, whether the instructions are clear, or whether someone can actually complete the process they came to your website to complete.
That difference is important.
Accessibility tools are useful. They are not the whole process.
This is not an anti-tool post.
I use tools. Most accessibility professionals use tools. If you are managing your own website, an accessibility checker can be one of the best places to begin learning how barriers show up online.
Tools are especially good at catching certain kinds of issues consistently and quickly. They can flag missing form labels, empty links, color contrast problems, heading issues, and code patterns that may create barriers. That matters because most small business owners do not have time let alone the know-how to inspect every line of code or manually test every page from scratch.
But an accessibility tool is not a final answer about whether a website is accessible. The W3C is very clear about this: tools can help identify potential problems, but knowledgeable human evaluation is still needed to determine whether a site is actually accessible. W3C’s accessibility evaluation overview explains why tools and human review need to work together.
That does not make your tool less valuable. It just means the score is a starting point, not a finish line.
A score cannot measure the whole experience
A high score can feel reassuring. I get it. We are used to scores telling us whether something is good, bad, complete, or in need of attention. But accessibility does not work that neatly.
A website can receive a good score from an automated tool and still be frustrating or impossible for someone to use. The tool may be checking the page that is currently visible, but not the menu that appears after someone clicks a button. It may identify that an image has alt text without knowing whether the alt text is meaningful. It may see that headings are present without knowing whether the page is organized in a way that helps someone find what they need.
It cannot know whether the language on your booking form is clear to a first-time visitor. It cannot tell you whether someone understands what will happen after they submit it. It cannot measure the hesitation, confusion, or extra effort a person experiences while trying to move through your website.
That does not mean those things are unimportant. It means they require a different kind of attention.
A tool can tell you where to look. A person has to decide what the finding means and what should happen next.
And this is where people often get stuck and get frustrated and/or overwhelmed.
They open a report and see a long list of issues. Some are labeled errors. Some are warnings. Some may be things the tool needs a human to check. It can feel like the only responsible response is to fix everything, immediately, in the order the report presents it.
That is rarely the best approach.
A report does not know which pages are most important to your business. It does not know whether your homepage, contact form, sales page, course checkout, or appointment scheduler is where people are most likely to encounter a barrier. It does not know which issue is keeping someone from completing an important task and which issue can be addressed as part of a larger cleanup.
You do. Or, at least, you are in the best position to find out. The work after the scan is to look at the results in context. Which pages matter most? What are people trying to do there? Where could friction stop someone from finding information, making contact, buying a product, joining a program, or accessing a resource?
Filter out all the extra “crap” that has you pounding your head on your desk and start with the basics. Once you’ve done that, you know what you may need help with from someone like a digital accessibility specialist. That is how a report becomes useful.
What comes after the scan
Let’s take a step back and look at what you do after you run the scan in a little more detail.
First things first, you take a breath and remind yourself that no matter what you don’t have to do “all the things” immediately. You start with what you know and what you can reasonably tackle on your own. Once you’re in the right headspace, you start clicking through the list.
Look at the issues it found, but do not stop there. Visit the page yourself. Move through it with only your keyboard. Read the headings in order. Check the form instructions. Think about the person who has never been to your website before and is trying to accomplish one specific thing. Then start with the barriers that affect the most important tasks.
If your contact form cannot be completed with a keyboard, that needs attention before you spend an afternoon correcting a decorative image. If the information people need is hidden behind vague link text or a confusing navigation menu, it may be more urgent than a warning on a page no one visits.
The goal is not to ignore the smaller issues but to understand what you are looking at well enough to make smart decisions about what to address first.
That is where tools become genuinely helpful. They give you evidence. They help you see patterns. They make it easier to catch repeat issues and confirm whether your fixes worked. They should support your judgment, not replace it.
Barrier-free design asks a different question
When we approach accessibility as a score to improve, it is easy to focus on the report instead of the people using the website.
Barrier-free design brings us back to the bigger question: Can someone use this? Not, “Did the checker pass it?” Not, “Is the score high enough?” But can a real person find what they need, understand what is in front of them, and complete the task without unnecessary friction?
That is why I do not believe the tool is the problem. The problem is the false confidence that can come from treating a tool as a substitute for thinking, testing, and listening. An automated scan can be a powerful part of your workflow. It just cannot be the entire workflow.
Run the scan. Learn from it. Fix what it helps you find.
Then keep going.
Because the goal was never a perfect score. The goal is a digital space that more people can actually use.
If you are still figuring out where to begin, start with what I mean by barrier-free design. The free BFDM™ Self-Assessment Quiz can also help you identify a next step that fits where you are right now.
