For charity websites, accessibility is the mission
A charity that exists to serve disabled and digitally excluded people cannot treat an inaccessible website as a technical debt item. It is the mission, failing quietly.
Commercial sites lose revenue when they are inaccessible. Charity sites lose the people they were founded to reach. When a charity's own copy promises support for people with complex needs, carers, and the digitally excluded, every unlabelled button on its website is a small breach of that promise, made in public, to exactly the wrong audience.
This is not an abstract risk. Around one in four people in the UK has a disability, and the populations charities serve skew older, poorer, and more reliant on assistive technology and older devices than the general public. For a meaningful share of a charity's beneficiaries, the accessibility of the website is not a quality attribute. It is whether the service exists.
The gap between values and markup
In audits of charity sites we see the same paradox repeatedly: warm, inclusive copy rendered in markup that excludes. The failures are rarely exotic. They are the basics, shipped without checking, and they are largely invisible to the sighted, mouse-using staff who approve the site.
- Icon and social links with no accessible name, announcing as bare URLs.
- Decorative graphics not hidden from screen readers, leaving a wall of “graphic, graphic, graphic”.
- Heading levels chosen for size, producing an outline that makes no sense to navigate.
- Pastel text and dividers that fail AA contrast for anyone with low vision.
- Carousels that auto-advance with no pause control.
- Form fields labelled only by placeholder text that vanishes on focus.
- Videos without captions, on pages aimed at the very audiences captions serve.
None of these is expensive to fix. All of them are expensive to have: each one filters out a slice of the audience, silently, at the exact point they tried to engage.
The regulatory and funding exposure
The Equality Act 2010 treats a website as a service; reasonable adjustments are not optional for charities, and “we didn't know” is not a defence a trustee board wants to test. The practical exposure is usually closer to home: funders increasingly ask about digital inclusion in grant applications, and a commissioner comparing two delivery partners can run a free automated scan in a coffee break. An inaccessible website is now a due-diligence finding, not a private technical detail.
WCAG 2.1 AA is the standard to hold the site against, not because the acronym impresses anyone, but because it is the benchmark public-sector bodies are already held to, the one funders reference, and a concrete definition of “accessible” that two people can check independently.
Why it slips, even on new sites
The uncomfortable pattern is that recently rebuilt charity sites are often the worst offenders. Rebuilds are bought as design projects, judged by screenshots, and signed off by people the site does not exclude. Accessibility appears in the brief as a value, not as acceptance criteria, so nothing fails when it is missing. The template ships with unlabelled icons, the decorative flourishes multiply, and the launch review never includes a keyboard or a screen reader.
The fix at the process level is one sentence in every web contract: conformance with WCAG 2.1 AA, verified before final payment, with an automated scan and a manual keyboard-and-screen-reader pass. Suppliers who build accessibly by habit will not blink. The ones who blink are telling you something useful.
Where to start without a budget
If the site is live today and money is tight, sequence it: run a free automated scan (axe or WAVE) to catch the mechanical failures; spend thirty minutes navigating your own donation and contact journeys with the keyboard alone; then fix the top of the funnel first, meaning the pages a first-time beneficiary or donor actually lands on. Automated tools catch perhaps a third of real-world problems, but that third includes many of the worst, and the scan is free.
What automated tools will not tell you is what the failures cost: which journeys they break, for whom, and what to fix first with a volunteer developer's ten hours a month. That prioritisation is the useful part of a human audit: severity times effort, against the journeys that matter, with the evidence attached.
A pro-bono offer for Welsh charities
We are a two-person product studio in Cardiff, and we keep a small number of pro-bono slots of our fixed-fee UX audit for registered charities in Wales: a full heuristic and WCAG 2.1 AA review of your live site, ranked by impact and effort, in exchange for permission to publish the audit as a case study. No obligation to hire us afterwards, and the report is written so any team can act on it. If your charity's website has not had honest eyes on it since launch, send us the URL.