Accessible Website Or Just Green Ticks?
When a website scores full marks with automated tools, most people breathe a sigh of relief. Green ticks mean the job is done or so they think. The truth is more complicated. A website that passes every automated test might still fail real users every single day. This blog explores why a technically compliant site can still be completely inaccessible, and why a genuinely accessible website is far more than box-ticking. We will also explore how strong website accessibility design comes from lived experience, not from software scans.
What Happens When You Trust The Ticks?
Let us begin with a true story. A respected academic organisation approached us recently. Their website had been built a few years ago with the best of intentions. Accessibility had been specified in the contract. The agency had followed what they believed were the correct guidelines. The end result was a website that passed every automated checker, zero errors flagged by WAVE, no major alerts, and all the expected ARIA tags in place. From a technical standpoint, it was an accessible website.
The Academic Sector And Its Accessibility Challenge
This was not a high street business or a small blog. This was a research organisation that supports academic collaboration across Europe and beyond. Around 50% of their members are located within the EU. That meant their website would fall under the scope of the European Accessibility Act, which is now in force. They were doing the right thing — proactively seeking to ensure compliance and usability. What they did not expect was the news we were about to deliver.
They Reached Out For Training, Not An Audit
Initially, they contacted us about providing accessibility training. They had a hunch that the website might have lost some of its accessible structure over time. They were not expecting major issues. They were just looking to brush up their skills and make a few improvements. Before we deliver any training, we always check the current site so we can tailor our sessions appropriately. That is when the alarm bells began to ring.
When A Website Looks Accessible But Is Not
We checked the site using screen readers and keyboard navigation. The moment we did, it became clear that this was not an accessible website at all. Critical navigation functions were inaccessible. Page structures were confusing. Landmark regions were either missing or incorrectly assigned. Interactive elements did not respond properly to assistive technology. The visual design looked clean, but the underlying structure had not been built with accessibility in mind.
Website Accessibility Design Needs More Than Code
This is the heart of the problem. Accessibility is not just a coding exercise. It is not just about putting ARIA labels in place or avoiding colour contrast errors. Real website accessibility design considers the full experience of disabled users. It is about understanding how someone navigates with a screen reader. How they use a keyboard instead of a mouse. How they interpret visual layouts, audio content, and interactive forms.
The Agency Had Done Their Best
This is not a story about blame. The agency that built the site had good intentions. They had built what they believed was an accessible website. They used automated checkers. They followed tutorials. They had read the guidelines. What they lacked was direct experience of what happens when a disabled person actually tries to use the site. That is not their fault. Most agencies have never worked with a team like ours, disabled testers who use real assistive tech every day.
An Accessible Website Is Not Just About WCAG Scores
The Web Content Accessibility Guidelines (WCAG) are essential. We work with them every day. But WCAG compliance is only part of the story. A site can technically meet many of the success criteria while still offering a poor or even impossible experience to users with disabilities. That is why true website accessibility design always combines standards with real-world testing. That is what separates a truly accessible website from one that just ticks boxes.
The Client’s Reaction: Shock, Then Action
When we met with the organisation and explained the issues, they were stunned. They had specified accessibility. They had received assurance that it had been delivered. Their trust had been misplaced, not maliciously, but through lack of understanding. To their credit, they immediately accepted the findings. They asked how to put things right, not just for compliance reasons, but because they genuinely cared about getting this right for their users.
Why This Story Matters
This story is important because it is so common. We see this again and again. Clients believe they have an accessible website because it passes automated tests. Agencies believe they have delivered accessibility because no errors show up on their scans. Yet real users struggle or cannot access core content. This disconnect causes legal risk, reputational damage, and exclusion — all of which could be avoided with the right support and training from the start.
The Limitations Of Automated Tools With An Accessible Website
Automated tools like WAVE, axe, and Lighthouse are helpful. We use them ourselves. They are good at flagging structural issues, missing labels, and colour contrast errors. However, they only catch around 30 percent of the issues that matter. They cannot understand meaning. They cannot simulate the experience of a blind user tabbing through a page. They cannot detect cognitive overload or ambiguous navigation structures. That is why accessible websites must always be tested by real users.
How We Help Clients And Agencies Alike
Our role is not to point fingers. It is to empower. We work with both clients and their developers to help everyone move forward. In this case, the agency had an ongoing support contract. Rather than excluding them, the organisation chose to include them in the remediation process. We will be auditing the site thoroughly, providing a roadmap for improvement, and offering training to both the client and the agency. This is website accessibility design in action — collaborative, informed, and focused on results.
Why Agencies Need Support With An Accessible Website Too
Most developers want to do the right thing. They are not trying to exclude people. They simply do not have the lived experience or the training to design with accessibility in mind. That is why audits, statements, and training are so valuable. They do not just help the client meet regulations. They build long-term capacity within the agency. Over time, this raises standards across the whole industry and leads to better outcomes for everyone.
How Accessibility Training Completes The Picture
Many of our engagements begin with accessibility training. That is because awareness is often the missing link. Teams do not realise what they do not know until someone shows them. Once they see the barriers, they are usually eager to fix them. Training provides practical knowledge, contextual understanding, and the ability to assess and improve future work. Combined with real-user audits, this creates lasting change.
The Impact Of European Law
For organisations operating in or trading with the EU, the stakes are now even higher. The European Accessibility Act is in force. This means websites must be accessible, not just in theory, but in practice. If your website excludes users with disabilities, you are at risk of fines, legal action, and reputational fallout. That is why now is the time to stop relying on green ticks and start focusing on true website accessibility design.
An Accessible Website Is A Process, Not A Checkbox
There is no magic switch that makes a site accessible overnight. It is a process. It involves testing, feedback, adjustments, and continual learning. That is why we work in partnership with our clients. We test with real users. We document issues clearly. We provide a valid Accessibility Statement that shows what has been done, what remains to be done, and when it will happen. This protects our clients while they make progress towards full compliance.
The Role Of Accessibility Statements
A good Accessibility Statement is not just a legal requirement. It is a shield. It shows that you are aware of your responsibilities, that you are taking action, and that you are engaging with the right support. This alone can make a significant difference if a complaint or investigation arises. It also builds trust with your users, especially those who may have experienced exclusion elsewhere.
How To Know If Have A Truly Accessible Website
If you want to find out whether your site is an accessible website, here are five questions to ask:
- Has it been tested by disabled users using assistive technology?
- Can all core functions be completed using only a keyboard?
- Does it follow consistent layout and heading structure?
- Are all forms, buttons, and links clearly labelled?
- Is there a roadmap and accessibility statement in place?
If the answer to any of these is no, your site may not be accessible, even if it passes automated tools.
What To Do If You Are In The Same Situation
If you discover your site is not accessible, do not panic. The key is to act. Start with a proper audit. Get real insight. Create a roadmap. Publish a compliant Accessibility Statement. Train your team. Work with your existing developers to apply the changes. You do not need to tear everything down. You just need a clear plan — and the right partner to guide you.
Let Us Help You Move Forward With An Accessible Website
At Access by Design, we specialise in turning confusion into clarity. We help organisations of all sizes build accessible websites that work for everyone. Our audits are led by real users.
Book yourself in for a chat today
