The Real Cost of an Inaccessible Nonprofit Website
Key takeaways
- An inaccessible website is a governance failure with legal, funding, credibility, and operational costs, not merely a design shortcoming.
- UK equality law requires service providers to make reasonable adjustments for disabled people (Equality Act 2010), widely understood to cover websites; the European Accessibility Act adds exposure where an NGO sells to consumers online in the EU.
- Institutional funders increasingly include digital accessibility in due diligence, so failures quietly cost funding relationships that are never explained to the applicant.
- A quarter of the UK population is disabled, so exclusion affects real donors, beneficiaries, trustees, and staff, and directly contradicts the mission of organisations serving disabled people.
- Retrofitting an inaccessible site is more expensive than building accessibility in, and the technical debt compounds the longer it is left.
- Present accessibility to the Board as a governance obligation with financial implications, weighing the cost of compliance against the larger cost of not complying.
Summary
An inaccessible website is not a design failure. For a registered charity or nonprofit, it is a governance failure with regulatory exposure, a credibility failure with institutional funders, and an operational failure for the beneficiaries, donors, and staff who cannot use the site effectively. The costs are real, specific, and largely invisible until something forces them into view: an accessibility complaint, a funding rejection, a journalist asking why the organisation that claims to serve people with disabilities has a website screen reader users cannot navigate. This post moves beyond the regulatory argument for accessibility and quantifies what an inaccessible website actually costs a nonprofit in practical terms. The costs include: legal exposure from complaints and enforcement actions, lost institutional funding from grant-makers who assess accessibility as part of due diligence, lost individual donations from donors with disabilities who cannot complete the donation flow, and reputational damage when the gap between stated values and actual accessibility is surfaced publicly. The post also covers the accessibility failures that are most common on nonprofit websites (colour contrast failures, missing alt text, keyboard navigation barriers, unlabelled form fields, and broken heading hierarchies) and explains why these failures persist even on sites that were WCAG-compliant at launch, through the ordinary accumulation of content changes made without accessibility awareness. The governance solution is not a one-time audit but an ongoing framework that prevents failures from accumulating in the first place.
An inaccessible website does not just exclude people. It exposes the organisation to legal action, can cost you institutional funding, and signals to funders that governance is not being taken seriously.
Most nonprofit leadership teams treat accessibility as a design consideration: something nice to have, addressed when budget allows. This is a misunderstanding of what accessibility failure actually means for an established organisation. The costs are financial, legal, reputational, and operational. They compound over time. And they are almost entirely invisible until something forces them into view.
The Legal Exposure Is Real and Growing
In the UK, the Equality Act 2010 requires service providers to make reasonable adjustments for disabled users (section 29, applying the section 20 duty). The duty is anticipatory: you are expected to plan for disabled users generally rather than wait for a complaint (Schedule 2). The Act does not name websites, but the Equality and Human Rights Commission's statutory Code of Practice on services (2011, paragraph 11.8) says a website may in itself be a service, and the Act's own Explanatory Notes use a website that must be checked for accessibility as a worked example. A website that cannot be navigated by keyboard, that lacks alt text, or that has forms without accessible labels can therefore fall short of that duty.
The European Accessibility Act, applying since 28 June 2025, adds digital-accessibility requirements for services sold to consumers in the EU. For an NGO that means selling online (a shop, ticketed events, paid training) rather than merely reaching European audiences. Penalties are set nationally and the Act fixes no figure (Article 30). See What the European Accessibility Act Means for NGO Websites for who it actually applies to.
In the United States, website accessibility lawsuits under the Americans with Disabilities Act are common: UsableNet, which tracks the filings, projects more than 6,000 in 2026. That is a US pattern, not a UK one, but international NGOs with US operations or US-facing digital properties are not exempt from it.
The legal risk is not theoretical. It is actuarial. The question is not whether accessibility complaints will be filed against nonprofit organisations. It is when, and whether your organisation will be ready to respond.
The Funding Cost You Never See
An inaccessible website sends a specific signal to funders: this organisation does not take inclusion seriously enough to invest in it. For NGOs whose mission involves serving disabled people, promoting equality, or delivering health and social services, the contradiction between mission and website is particularly damaging.
The cost is invisible because a funder who passes on an application does not explain why. You never know which funding relationships failed to start because of something on your website.
The People You Are Excluding
In the UK, 25% of people, about 16.7 million, are disabled under the Equality Act definition (Family Resources Survey 2024 to 2025). In the EU, around 90 million people live with a disability. These are not edge cases. They include your donors, your beneficiaries, your Board members, your staff, and the journalists and regulators who evaluate your organisation.
A website that cannot be navigated by screen reader excludes blind and visually impaired users. A website with insufficient colour contrast excludes users with low vision. A website without keyboard navigation excludes users with motor impairments. A website with no captions on video content excludes deaf and hard-of-hearing users.
For nonprofits, this exclusion is not just an accessibility failure. It is a mission failure. If your organisation exists to serve people, and especially if it serves people with disabilities or advocates for inclusion, an inaccessible website contradicts the institutional purpose you are funded to deliver.
The Operational Cost of Retrofitting
Accessibility is cheapest when built in from the start. Retrofitting an inaccessible website (fixing heading hierarchies, adding alt text to hundreds of images, rebuilding forms with accessible labels, implementing focus management, resolving colour contrast across every page) is more expensive than building accessibility into the foundation.
For websites built without any accessibility consideration, the remediation cost can approach or exceed the cost of rebuilding on an accessible framework. This is the technical debt dimension of accessibility failure: every month that passes without addressing it increases the eventual cost of compliance.
The Lumos framework I use for Webflow builds addresses this at the architectural level: an accessible structure is built into the page templates, component library, and interaction patterns, so the most expensive structural failures do not arise by default. Individual content still needs accessible authoring (descriptive alt text, correct heading structure, meaningful link text), which is where conformance is ultimately won or lost.
What Accessibility Compliance Actually Costs
The cost of accessibility depends entirely on where you are starting from.
For websites built on accessible frameworks: Ongoing compliance is primarily a content discipline. Training the team to write descriptive alt text, maintain heading hierarchy, and check colour contrast on new content. Cost: minimal, integrated into normal workflows.
For websites with isolated accessibility failures: Missing alt text, some contrast issues, form labels needed. This is the common case: the WebAIM Million 2026 analysis found detectable WCAG 2 failures on 95.9% of the top million home pages, and six error types (low-contrast text, missing alt text, unlabelled form fields, empty links, empty buttons, missing document language) account for 96% of the errors. These can be remediated on the existing site without rebuilding. Cost: typically a few days of focused work.
For websites with systemic accessibility failures: Broken heading hierarchy across all templates, no keyboard navigation, no focus management, no skip links. Remediation may cost more than rebuilding on an accessible framework. Cost: variable. A structured diagnostic like the Blueprint Audit can establish which case you are in before you commit to a route.
The common objection is that accessibility is expensive. The more accurate statement is that inaccessibility is expensive: in legal risk, lost funding, excluded users, and compounding technical debt. Compliance is an investment that reduces institutional risk and expands your reach simultaneously.
Making the Case to Your Board
Present accessibility as a governance obligation with financial implications, not as a technical improvement request.
The framing that works: accessibility compliance reduces legal risk under the Equality Act (and the EAA where the organisation sells to consumers online in the EU), meets growing funder expectations for institutional credibility, serves more of the people your organisation exists to help, and prevents the accumulation of technical debt that makes future compliance more expensive.
If a Board member asks whether the organisation can afford to invest in accessibility, the counter-question is whether the organisation can afford the regulatory, financial, and reputational cost of not doing so.
For the technical details of WCAG AA compliance on Webflow, see WCAG AA Accessibility on Webflow. For the accessibility statement your organisation needs, see Accessibility Statement Template for Nonprofits. For how the European Accessibility Act specifically applies to NGOs, see What the European Accessibility Act Means for NGO Websites.
Two clicks. Three things.
Send the address of your website. Within two working days you get a short email naming the three things a funder would hold against it, including what AI assistants like ChatGPT and Google’s AI Overviews currently say about you. No report, no call, no follow-up unless you ask.
Received. Your three things arrive within two working days.
That did not send. Email hello@socialectric.com with your website address and I will reply from there.
Frequently asked questions
- Can a nonprofit be sued for an inaccessible website?
Yes. Under the UK Equality Act 2010, organisations providing services to the public must make reasonable adjustments for disabled users, and the Equality and Human Rights Commission's statutory Code of Practice says a website may itself be a service. In the EU, the European Accessibility Act creates additional legal obligations where you sell to consumers online. In the US, UsableNet projects more than 6,000 digital accessibility lawsuits in 2026; that is a US pattern, not a UK one.
- How much does WCAG compliance cost for a nonprofit website?
It depends on the starting point. Websites built on accessible frameworks need only content-level maintenance. Websites with isolated failures need targeted fixes costing a few days of work. Websites with systemic structural failures may need rebuilding, which is more cost-effective than extensive retrofitting.
- What happens if we receive an accessibility complaint?
Under the Equality Act, you are expected to make reasonable adjustments. Under the EAA, each member state designates an authority to follow up complaints and verify corrective action, and penalties must be accompanied by remedial action. Having a published accessibility statement, a documented compliance roadmap, and evidence of ongoing monitoring demonstrates good faith.
- Is accessibility compliance a one-time project?
No. Accessibility requires ongoing attention. New content, new pages, and platform updates can introduce accessibility failures. A quarterly automated scan plus an annual manual review is the minimum governance cadence.
- Do institutional funders check website accessibility?
Increasingly, yes. Major trusts and foundations include accessibility in their due diligence criteria, particularly for organisations working in disability, health, and social services. An inaccessible website signals governance gaps that affect funding decisions.
- What are the most common accessibility failures on nonprofit websites?
Missing image alt text, insufficient colour contrast, forms without accessible labels, broken heading hierarchy, no keyboard navigation support, and missing accessibility statements. These are also the easiest and cheapest failures to fix; see what WCAG 2.2 AA asks of a nonprofit site.
- Does Webflow support WCAG AA accessibility?
Webflow as a platform supports accessible builds, but does not guarantee accessibility by default. The Lumos framework adds an accessible foundation layer: correct heading structure, focus management, semantic markup, and keyboard-navigable components. Content-level accessibility still requires correct authoring practices; see WCAG AA accessibility on Webflow.
- Should we mention accessibility in our annual report?
Yes. Reporting on digital accessibility demonstrates governance maturity and signals to funders that the organisation takes compliance seriously. Include the standard you are working to, any audits conducted, and improvements made during the reporting period.
- Is an accessibility overlay or widget sufficient for compliance?
No. Accessibility overlays do not fix underlying code issues, and the Overlay Fact Sheet, signed by WCAG and ARIA specification contributors, states that no overlay product can bring a website into conformance with any accessibility standard. They can actually make the experience worse for users who rely on assistive technology. The only reliable path to compliance is fixing the website itself.
- What is the first step we should take?
Run a free automated accessibility scan using the axe DevTools browser extension on your homepage, a programme page, and your donation page. This gives you a baseline. Then publish an accessibility statement and establish a remediation plan. For a structured approach, the Blueprint Audit includes a full accessibility assessment.