When is a website finished? Avoiding accessibility erosion
There is a point during most website projects that feels like an end is in sight. This might be shortly before launch, or even shortly after.
After months of work you might find yourself in a good place. Colleagues have been trained in the new content management system. Content has been rewritten. Headings are structured, colour contrasts pass, focus states are visible and the keyboard reaches every control. The build does what it promised to do.
But an accessible website is not a state you arrive at. It’s a state that must be maintained.
Having received sign-off, a new event listing is published. Then another. Then a hundred more. Each one is a chance to reintroduce a barrier that the technical foundation, however well built, was never in a position to prevent.
This is the quiet gap at the heart of digital accessibility: the difference between accessibility that’s genuinely embedded and accessibility that merely passed.
The scope of the technical foundation
A well-built website gives content authors an accessible foundation to publish on. It’s worth being clear about where the platform’s job ends and the author’s begins.
Any website or content management system design and build will have undertaken accessibility auditing and usability testing to ensure the framework incorporates guidance from users with lived experience.
A good foundation can enforce a logical heading hierarchy in its templates. It can ship colour palettes that meet contrast requirements. It can build forms with proper labels, error handling and keyboard support. It can generate valid, robust, semantic markup that tell assistive technologies the type of content being presented.
Through considered use of semantic code, many accessibility failures can be prevented. But code is only part of the story. The code of a website is a decision made once by its developers and designers and remains consistent regardless of the content.
Where the erosion begins
Content is authored by people. In the arts, many people are time-poor, wearing multiple hats and working to strict deadlines. With the best will in the world, accessibility errors are inadvertently published on a daily basis.
Accessibility drift rarely arrives as one dramatic failure. It accumulates through ordinary publishing processes. People don’t purposefully exclude their users, but may create barriers daily through lack of awareness or system constraints.
This includes:
- Uploading an image without alt text or where the alt text is a file name such as “image123.jpg”. A blind visitor will be aware an image is there, but learn nothing about its contents.
- Launching a season brochure by uploading an inaccessible PDF. This might include scanned images, untagged elements and illogical reading orders. All of which make it harder for users to interact with its contents
- Headings used for appearance rather than their meaning. Using font-size or bolding text might give the visual appearance of a section title, but screen reader users navigating by heading will not be able to find these.
- Link text reading “click here” or “read more” repeated throughout a page. Out of context it is very difficult to identify where these links would take you.
- A hired event or touring production’s image providing information with no text alternative. (Panto anyone?)
None of these break the structural wins the build gave you. But the platform contains the tools necessary to create accessible content on an ongoing basis.
Despite an accessible foundation, introducing new issues like this each time a page is published presents new access barriers every week.
A debt you did not know you were taking on
Projects have three core constraints. Time, cost, and scope. When under pressure, with no additional time or budget website projects may be descoped before launch.
Imagine a team under pressure to launch. They take a shortcut, something quick and untidy that works for now, promising themselves they will tidy it up later. They have not avoided the work. They have borrowed against it. And like any loan, the debt charges interest: the longer the shortcut sits there, the more gets built on top of it, and the more expensive it becomes to put right.
What would have taken an hour on day one takes a week a year later.
Accessibility erosion is the content team’s version of the same debt.
Every image published without alt text is a small loan. Every scanned PDF, every “click here” link, or banner text saved as an image. No single one feels like borrowing. Each takes seconds to skip and saves a busy person a small amount of effort on a deadline.
But the interest compounds.
First, it is paid by your visitors, every day, in the form of barriers: the page that cannot be navigated, the download that cannot be read, the link that leads nowhere anyone can name.
Second, it is paid by your organisation when the bill finally comes due, because fixing one missing alt text at the moment of publishing takes ten seconds. Fixing three years worth of alternative text means auditing thousands of pages, prioritising and planning the remediation work, and trying to evolve your processes to stop the process from repeating itself.
The cheapest moment to pay accessibility debt is the moment before it is created.
Why an audit in isolation isn’t enough
Automated accessibility checks are a useful tool, when used in combination with manual assessment, but they are only effective at finding up to 30 – 50% of potential accessibility issues.
Is there a label on this input field? Does this text meet contrast ratios? Are there animations without a way to pause them? These are exactly the parts a good technical foundation has already handled.
The failures above live somewhere else.
Whether alt text is meaningful rather than merely present. Whether a heading describes what follows it. Whether a link makes sense out of context. Whether a PDF can be read at all. These are judgements about content, and judgement is not something an audit can automate.
A tool can tell you an image is missing alt text. It cannot tell you if the alt text you wrote makes sense in the context you’ve used it.
So a site can pass its checks on the day it launches and fail its users six weeks later. Without an accessible authoring process in place and without regular monitoring, the debt grows.
Accessibility is a practice, not a purchase
The reframe worth holding onto is this: accessibility is not something you complete once. It is a practice you sustain, and it belongs to the people who create content as much as the people who design the site and write the code.
The technical work and the training work are not alternatives. They are two halves of the same thing. The build makes accessibility possible by removing the structural barriers. The people make it real by not reintroducing them, one publish at a time.
In practice, sustaining accessibility looks less like a project and more like a habit:
- Build accessibility into the content templates and house style guide, so the accessible choice is the default choice.
- Give the people who publish, a working grasp of the principles: what alt text is for, why heading order matters, what makes a link legible out of context.
- Treat accessibility as part of the definition of “done” for a piece of content, alongside spelling and brand.
- Conduct more frequent accessibility audits to prevent a backlog of issues, rather than trusting that a launch-day audit still describes a site that has changed a thousand times since.
Each of these habits is, in debt terms, a repayment plan: small, regular instalments that stop the balance from ever becoming frightening.
The floor and the room
A solid technical foundation gives you an accessible floor. That is genuinely valuable, and organisations that have one are ahead of most.
But the experience your audience has is built in the room above it, in every listing, image, document and link your team publishes after the developers have gone home.
Good tools and good practice go hand in hand. The technology clears the structural barriers so your people do not have to. Your people keep the content clear so the technology’s work is not quietly undone. Neither finishes the job alone.
So, when is a website finished? It isn’t. And the sooner accessibility is understood as an ongoing practice rather than a box that was ticked at launch, a debt repaid steadily rather than left to compound, the longer that clean audit will keep describing something true.
Need support to make accessibility your practice?
Building an accessible digital presence takes time, and it helps to have a guide.
We specialise in helping organizations move beyond “ticked boxes” to sustainable, inclusive habits.
Whether you need an accessibility audit to establish your current baseline, team training to empower your content editors, strategic consultancy, or inclusive usability studies to ensure your framework reflects the lived experience of your users, we can help.
Get in touch to talk about how we can support your ongoing commitment to access.