Beyond compliance: What real web accessibility looks like
Last week, I had a fascinating chat with accessibility consultant and expert Dean Frank Reynolds. We talked about the European Accessibility Act (EAA) and what it means for our clients, most of whom are NGOs and public sector organisations. What came out of our conversation was something we've suspected for a while: True accessibility goes far deeper than simply passing automated tests.
Not stopping at checklists
We've always made sure our websites pass the standard checks. Proper colour contrast ratios, semantic heading structures, and high scores on tools like WAVE and Lighthouse. But Dean made a point that stuck with me: "You can make a completely blank website pass all these checks."
He's right, of course. I've seen sites that technically meet WCAG AA standards but are still a nightmare to navigate.
Dean showed me an example from one of our client sites where we had a product page that listed out some relevant services with a link to view all services. This makes perfect sense from a design perspective. But what if you're using a screen reader and want a different service? You'd need to click through "Services" first, then hunt for the service you are looking for. It works, but adds an unnecessary step to the user journey that is even more challenging for people using assistive technology.
This resonated with me. Accessibility isn't just about meeting WCAG guidelines, it's about understanding how real people interact with websites.
There’s no universal solution
Dean mentioned knowing several people with dyslexia, and roughly half of them love those dyslexia-friendly overlays whilst the other half "hate overlays with a passion”.
We've seen this complexity firsthand when working with organisations like the WHO and various NGOs. What works brilliantly for one person might be completely wrong for another.
Take the new Advanced Perceptual Contrast Algorithm (APCA) that's emerging alongside traditional WCAG guidelines, which can seemingly gives contradictions for colour choice. Our approach has been to test with real users wherever possible, and feels refreshingly honest in a field that often pretends there are clear right and wrong answers.
Making it standard practice
Rather than treating accessibility as something you bolt on at the end (or worse, charge extra for), we're building it into our component libraries from the start. As Dean put it: "You'll start to develop accessible templates. So then everything that you build past this point is accessible as the standard." That's exactly where we've ended up with projects like the Crop Trust and Proforest sites. The accessibility isn't retrofitted. It's baked into every component we create.
We also offer regular accessibility audits as part of our retainer services. This is a fundamental part of how we maintain and improve websites over time, rather than a box-checking exercise.
The human element
What struck me most about our conversation was Dean's emphasis on intent and understanding. He shared experiences of encountering well-meaning but misguided attempts at inclusion. Dean gave a real world example of grab rails installed behind toilets in disabled bathrooms, as well as people using outdated terminology.
We see similar things in web design. Good intentions, but missing the mark because there's not enough actual understanding of how people use these sites.
When accessibility issues do arise (and they inevitably will), the response matters. As Dean noted: "I would hope that any decent company of any size would apologise and attempt to fix the issue."
Beyond accessibility legal requirements
Whilst the EAA has created urgency around accessibility compliance, it’s worth noting that the majority of organisations will fall below the legislation's thresholds (under 10 employees or €2 million turnover). But that doesn't mean they shouldn't prioritise accessibility.
But should that matter? Dean made the point that accessibility is “becoming a competitive edge”. For organisations working on climate change or global health, missions that are fundamentally about helping people, excluding users with disabilities, seems to miss the point entirely.
Plus, we've noticed that accessible design often just makes websites better for everyone. Clear navigation helps all users, not just those using screen readers. Good colour contrast makes sites more readable on phones in bright sunlight. Semantic HTML helps with SEO.
Our approach to web accessibility
Our conversation with Dean reinforced something we've been thinking about for a while. Real accessibility isn't about hitting 100% on automated tests. It's about understanding how actual people use your website.
We've built up our knowledge through years of working with organisations that serve global, diverse communities. The technical standards are important, obviously. But the real skill seems to be in thinking beyond the checklist to consider genuine user needs.
There's still plenty we're learning. The field keeps evolving, new standards emerge, and user expectations change. My conversation with Dean was a timely reminder of why this work matters, and why it's worth getting right.
-
Matt Keogh
Creative Director and Co-owner
