Why accessibility audits alone don't create accessible organisations
.jpeg)
Accessibility audits help identify WCAG issues, but many organisations discover that the same accessibility problems return in future products. An accessibility audit (also known as an accessibility review, accessibility assessment or WCAG audit) is a structured accessibility evaluation of a digital product against the Web Content Accessibility Guidelines (WCAG). It identifies barriers such as insufficient colour contrast, missing labels or keyboard navigation that doesn’t work, and recommends how to fix them. But this kind of digital accessibility audit only captures a single moment in time: when the same issues keep coming back, it’s usually because accessibility knowledge stays within one project instead of becoming part of how the organisation works.
1. What happens after an accessibility audit?
Sometimes I find myself wondering what happens after we deliver an Accessibility Audit Report. We identify accessibility issues based on the WCAG, document them with examples and provide recommendations for implementation. The team works through the fixes, and the product becomes more accessible. A few months later, I come across another product from the same organisation and notice some of the same issues again: insufficient colour contrast, missing labels and keyboard navigation that still doesn't work as it should. It feels as though the knowledge never made it beyond the previous project. And that makes me wonder:
If an accessibility audit improves a product but doesn't change the way an organisation learns, are we really solving the problem?
I think part of the answer lies in the way accessibility auditing typically comes about. There is almost always a specific trigger:
- The European Accessibility Act has come into force, and the organisation needs to demonstrate compliance;
- A contract requires compliance with the WCAG;
- An accessibility-related complaint has been raised;
- A key client has brought the topic to the table.
All of these are perfectly valid reasons. However, they also mean that accessibility audits are often treated as a response to a specific problem. The focus is on fixing that one product, at that moment in time. Given deadlines and competing priorities, that is entirely understandable.
2. Why accessibility knowledge disappears after audits
The problem is that organisations can easily fall into a difficult cycle to break: audit, fixes, new product... and then another audit to address many of the same issues. In practice, the learning often remains within the team that worked on that project. It rarely reaches the teams building the next one. Today, many organisations work in autonomous, cross-functional teams. This has many advantages, but it also means that knowledge does not always flow naturally across projects. And accessibility depends on exactly that.
3. Signs your organisation isn’t learning from accessibility audits
A few patterns tend to signal that accessibility knowledge isn’t sticking:
- The same WCAG issues reappear in new products
- Teams repeat mistakes that were already solved elsewhere
- Accessibility testing only happens after products go live, to comply with legislation
- Products aren’t tested with assistive technologies such as screen readers
- Accessibility is only checked against WCAG, never validated with people with disabilities
- Knowledge stays locked inside a single project or team
- Your Design System isn’t accessible by default
Even when organisations invest in training, ongoing support and documentation, why does this knowledge still struggle to spread across the organisation?
4. How to retain accessibility knowledge
At Hyphen, we've been exploring a few ways to build accessibility maturity and address this challenge:
a. Embedding accessibility into everyday work
One way to prevent knowledge from being confined to a single project is to embed accessibility into everyday ways of working. When teams are supported as they design, develop and validate their own products, learning becomes far more continuous and meaningful than it would through a single training session. This validation is most powerful when it goes beyond technical checks to include usability testing with people with disabilities, whose real experience surfaces barriers that WCAG conformance alone can miss. Looking at an entire user journey also makes it easier to recognise that many seemingly different issues often stem from the same underlying cause. Accessibility stops being something that's addressed at the end of the process and instead becomes part of how products are built from the start.
b. Using Design Systems as a foundation
Design Systems can also play an important role in sharing accessibility knowledge across teams. When core components already incorporate accessibility best practices and are supported by clear documentation, teams no longer need to solve the same problems repeatedly. Of course, this depends on the Design System being kept up to date and consistently adopted across projects.
c. Creating bridges between projects
Another approach is to have someone who helps knowledge flow across teams. This doesn't have to be a dedicated accessibility specialist. It simply needs to be someone with enough context to recognise recurring patterns and say, "We've seen this issue before. Let's build on what we learned." In this way, solutions stop belonging to a single project and instead benefit the whole organisation.
d. Creating opportunities for teams to share knowledge
Giving teams more opportunities to share their experiences could also make a difference. Giving people the space to talk about the challenges they've faced, what worked well, what didn't, and what they would do differently helps knowledge spread across the organisation. Over time, these conversations contribute to a culture of continuous learning (the basis of a lasting accessibility strategy) and reduce the likelihood of the same accessibility issues appearing again.
5. Final thoughts
All of this requires investment. It takes time. But continuing to fix the same accessibility issues over and over again also comes at a cost. Every organisation is different, and there is no universal solution.
Maybe it comes from my background in Ergonomics, but I've grown used to looking for the root cause of problems before thinking about how to fix them. When it comes to accessibility, I still believe the greatest impact doesn't come from fixing issues alone, but from creating the conditions to prevent them from happening again.
Related reading
More from the Hyphen team on building and maintaining accessible products:
Work with us on accessibility
If you’d like to move from one-off fixes to lasting accessibility and digital inclusion, we’d love to help you get there.
- Explore our services
- Talk to our accessibility specialists
FAQs
Is an accessibility audit enough to ensure accessible products?
An accessibility audit is a strong starting point. It identifies accessibility barriers at a specific moment and shows you exactly what to improve. To stop the same issues from reappearing in future projects, it works best as part of a wider, ongoing process.
Why do the same accessibility issues keep recurring?
Because the knowledge generated during an accessibility audit is not always shared across teams or embedded into the organisation's processes, components and ways of working.
How can organisations retain the knowledge gained from an accessibility audit?
By embedding accessibility into product development, using accessible Design Systems, creating opportunities for teams to share knowledge, providing ongoing support and light accessibility governance throughout projects.
What role do Design Systems play in accessibility?
When the components in a Design System already incorporate accessibility best practices and are supported by clear documentation, teams can build new products more consistently, strengthening UX accessibility while avoiding the same mistakes.
Are accessibility audits still important?
Absolutely. Accessibility audits are essential for identifying barriers and improving your existing products and they deliver even more value when the knowledge they generate helps shape how your whole organisation designs and builds digital products.
.jpeg)