“We’re already web accessible” - a phrase that always makes me pause
I hear it quite often in conversations about web accessibility and every time I wonder - what do you actually mean by “already accessible”?
Because in reality, this phrase often means something very different, here’s what it might mean:
1️⃣ “Nobody complained”
Silence is not proof of accessibility.
Most users won’t contact support to explain they couldn’t navigate with a keyboard, complete a form using a screen reader, read low-contrast text or use your site at 200% zoom.
They just leave, sometimes to a competitor.
2️⃣ “We finished an accessibility audit”
Great start, but accessibility is not a one-time project.
Websites evolve constantly with new content, redesigns, features, third-party widgets, urgent fixes and accessibility issues often come back.
An audit is a milestone, not the finish line.
3️⃣ “We invest money in accessibility”
Budget matters, but spending money alone doesn’t create sustainable accessibility.
Without ownership, monitoring and clear processes, teams often end up fixing the same issues repeatedly instead of preventing them.
4️⃣ “Our team had an accessibility training”
Training helps, but if it happened once, knowledge fades.
Teams change, new developers join, designers leave, priorities shift... If accessibility isn’t part of onboarding, reviews, and daily work, momentum disappears.
5️⃣ “We have accessibility documentation”
It’s great, but does the team actually use it?
Sometimes guidelines live quietly in a forgotten folder and nobody uses them. Documentation matters, but regular discussions and shared ownership matter more.
I’ve noticed that the organisations that truly invest time and efforts in web accessibility never say: “We’re already accessible”.
Instead, they say: “We’re improving” or “We’re working on this continuously”, because they understand something really important: accessibility is not a checkbox, not a project with an end date and not the responsibility of one person.
It’s an ongoing journey, just as important as web development itself.
Like performance, security or quality, accessibility requires everyday effort from the whole team: developers, designers, content creators, QA, product owners, leadership. It’s not about reaching perfection, but more about continuous attention and improvement.
Have you heard the phrase “we’re already accessible”? What did it actually mean in reality?