What the European Accessibility Act Means for NGO Websites
Key takeaways
- The European Accessibility Act applies from 28 June 2025 and can bite on an NGO where it sells to consumers online in the EU: a shop, ticketed events, paid training. Operating in Europe, fundraising, or running programme pages is not, on its own, a trigger.
- The relevant technical standard is EN 301 549. The version currently cited in law (V3.2.1) maps to WCAG 2.1 AA, so WCAG 2.1 AA is the sensible technical baseline. V4.1.1, published September 2026, adopts WCAG 2.2, but it is not yet cited in the Official Journal, so no harmonised standard yet gives an automatic presumption of EAA conformity.
- Where a service is in scope, the provider must explain how it meets the accessibility requirements in that service's terms and conditions, with evidence that the process is monitored (Article 13 and Annex V).
- Microenterprises providing services are exempt (fewer than 10 people, and turnover or balance sheet not over €2m), but the size test only matters once a service is in scope in the first place.
- Enforcement is largely complaint-driven and varies by country, with exposure growing for NGOs providing in-scope services across several member states.
- The Board should treat the Act as a governance obligation, beginning with an audit to establish a baseline and a remediation plan that fixes critical failures first.
Summary
The European Accessibility Act applies from 28 June 2025 and requires certain digital services sold to consumers in the EU to meet EN 301 549, the European standard whose harmonised version incorporates WCAG 2.1 AA. Its scope is a closed list (Article 2); for an NGO the relevant category is e-commerce, meaning selling goods or services to consumers online. A purely informational or donation-only site is very unlikely to be caught, and 'operating in Europe' or reaching EU audiences is not itself a trigger. This post explains who the Act actually applies to, what EN 301 549 requires in practice, what the penalty regime does and does not say, and how to treat accessibility as a Board-level governance obligation. UK charities have Equality Act 2010 duties regardless, and funders increasingly expect accessibility whether or not the Act formally applies.
If your NGO sells to consumers online in the EU (a shop, ticketed events, paid training, paid publications), the European Accessibility Act can apply to that service. It has been enforceable since 28 June 2025 (Article 31). What it does not cover is a purely informational or donation-only site: nothing in the Act turns on operating in Europe, accepting donations, or running programme pages for European audiences.
Most nonprofit communications teams are unaware of it. The EAA was written for commercial digital services, and its scope is a closed list (Article 2): electronic communications, audiovisual-media access, certain transport services, consumer banking, e-books, and e-commerce. For an NGO the relevant category is e-commerce, meaning selling goods or services to consumers online. Programme delivery, fundraising, and offering information to European audiences are not, on their own, on that list.
This is general information to help a Board scope the issue, not legal advice. Whether the Act applies to a particular organisation depends on the services it offers and the member states involved, so confirm it with a qualified adviser before relying on it.
Here is what your Board needs to understand.
What the European Accessibility Act Is
The European Accessibility Act (Directive (EU) 2019/882) is EU-wide legislation requiring certain digital products and services to be accessible to people with disabilities. It was adopted in 2019 and applies from 28 June 2025; member states were required to transpose it into national law by 28 June 2022 (Article 31), though several did so late.
The EAA is a directive, not a regulation: each member state transposes it into national law, so enforcement, penalties and complaint processes vary by country. The relevant technical standard is EN 301 549, whose currently cited version (V3.2.1, 2021) maps to WCAG 2.1 Level AA. V3.2.1 is harmonised under the separate Web Accessibility Directive, not under the EAA. V4.1.1, published in September 2026, is the first version written as a harmonised standard for the EAA and it moves to WCAG 2.2, but its own foreword is conditional: a presumption of conformity follows only "once the present document is cited in the Official Journal of the European Union". It has not been cited yet. So treat WCAG 2.1 AA as the sensible technical baseline rather than an automatic proof of EAA conformity, and expect the reference level to move to 2.2 when the citation lands.
For practical purposes, meeting WCAG 2.1 AA covers most of the technical substance the EAA is concerned with, though no harmonised standard yet makes that an automatic proof of conformity. Where the EAA applies to a service, the Directive also requires the provider to include, in that service's terms and conditions, a description of how it meets the accessibility requirements and information showing the delivery process and its monitoring keep it compliant (Article 13 and Annex V). That is a duty to document and explain, rather than a separate public-sector accessibility statement.
Does the EAA Apply to Nonprofits?
The EAA targets commercial operators. A microenterprise (fewer than 10 people, and either turnover or balance-sheet total not exceeding €2 million, Article 3(23)) that provides services is exempt from the directive's service obligations (Article 4(5)). That size test only matters once a service is within the Article 2 scope in the first place.
However, there are important caveats for NGOs.
You are outside the microenterprise exemption if you have 10 or more people, or if you exceed both the €2 million turnover and balance-sheet thresholds (Article 3(23)). But that only brings a service into scope where it is on the Article 2 list, which for an NGO means selling to consumers online. Many established international NGOs run online shops, ticketed events or paid training that fall within it.
Public funding does not decide it. The EU Web Accessibility Directive (2016/2102) applies to public sector bodies, not to every publicly funded organisation, and it expressly excludes the websites of NGOs (Article 1(3)(b)) unless they provide services essential to the public, or services that specifically address the needs of people with disabilities. An NGO delivering that kind of service can be caught by it; most others are not.
If you sell in multiple EU countries, each of those countries can enforce the EAA independently. A complaint filed in France does not prevent a separate complaint in Germany, and exposure grows with the number of markets in which you actually sell.
Even if the EAA does not technically apply to your organisation, meeting its requirements is increasingly expected by institutional funders, EU-based partners, and regulators. The direction of travel is clear: accessibility compliance is becoming a baseline expectation for any organisation operating in or receiving funding from Europe.
What EN 301 549 Requires
EN 301 549 is the European standard for digital accessibility. The version harmonised to date (V3.2.1, under the Web Accessibility Directive) maps to WCAG 2.1 Level AA and adds requirements specific to European regulation, including ICT beyond the web. The areas most relevant to nonprofit websites are:
Perceivable content. All images must have descriptive alt text. Videos must have captions and audio descriptions. Colour contrast must meet 4.5:1 for normal text and 3:1 for large text, large meaning 18pt or 14pt bold. Content must remain readable when text is resized to 200%.
Operable interfaces. Every interactive element must be accessible via keyboard. Focus indicators must be visible. Users must have enough time to read and interact with content. Nothing on the site should flash more than three times per second.
Understandable content. The language of the page must be declared in the HTML. Forms must have clear labels and descriptive error messages. Navigation must be consistent across the site.
Robust markup. Every interface component must expose its name, role and value to assistive technology, and status messages must be announced without moving focus. ARIA attributes, where used, must be correctly implemented. The site must work with current screen readers and other assistive tools. Note that 4.1.1 Parsing is now treated as always satisfied for HTML and XML content, so "valid HTML" is no longer the test it once was.
Enforcement and Penalties
Enforcement is complaint-driven in most member states. Article 23 requires each member state to run procedures that check the compliance of services, follow up complaints, and verify that the operator has taken the necessary corrective action. Regulators are not systematically auditing every website, but when complaints are filed, investigations follow.
Penalties are set nationally, not at EU level. Article 30 requires them to be effective, proportionate and dissuasive, to be accompanied by effective remedial action, and to take account of the seriousness of the non-compliance and the number of people affected. It sets no figure and no percentage of turnover. Actual exposure depends on which member state is enforcing.
The practical risk for most nonprofits is not an immediate fine. It is a complaint from a user, a partner organisation, or an advocacy group that triggers an investigation, requires resources to respond to, and creates reputational exposure precisely when the organisation is seeking to demonstrate institutional credibility.
What Your Board Needs to Know
The EAA is not a technical issue for the web team to handle. It is a governance obligation that the Board should be aware of, particularly for organisations that operate internationally, receive EU funding, or serve European audiences.
Present it to Trustees in three parts. First, the regulatory landscape: the EAA is enforceable, the UK Equality Act 2010 already creates domestic accessibility obligations through the duty to make reasonable adjustments and the services provisions, and institutional funders are increasingly including accessibility in due diligence. Second, the current state: commission an accessibility audit (even a basic automated scan with axe DevTools) to establish where the organisation stands. Third, the recommended action: a structured remediation plan that addresses critical failures first and establishes ongoing compliance monitoring.
The cost of compliance is usually lower than organisations expect: most failures are a finite, fixable list. The cost of non-compliance is unpredictable, covering complaint investigations, remediation under time pressure, reputational damage, and lost funding opportunities. The Real Cost of an Inaccessible Nonprofit Website sets out what that bill looks like in practice.
Practical Steps for NGOs
Audit your current site. Run axe DevTools on your homepage, a programme page, and your donation page. Note the number and severity of violations. This gives you a baseline.
Document how the service meets the requirements. Where the EAA applies, that information belongs in the service's terms and conditions (Article 13 and Annex V). See Accessibility Statement Template for Nonprofits for the same ground under a UK charity's Equality Act duties.
Implement a complaint mechanism. This can be as simple as a dedicated email address for accessibility feedback, linked from your accessibility statement.
Address critical failures first. Missing alt text, broken keyboard navigation, insufficient colour contrast, and unlabelled form fields are the most common failures and the easiest to fix.
Establish a review cadence. Build a quarterly review into your website governance schedule. See How to Create a Website Governance Policy.
The Blueprint Audit includes a full WCAG AA accessibility assessment as part of the technical audit.
For how WCAG AA compliance works in a build, see WCAG 2.2 AA checks for charity and nonprofit websites. For the broader governance context, see WCAG Accessibility as a Nonprofit Governance Obligation.
Free download
Your website, for the board.
A two-page briefing you can fill in and put in the next board pack. It covers the six things funders check, how to see what AI tools say about you, and the options to put to trustees.
That did not send. Email hello@socialectric.com and we will send you the briefing. The spam check did not finish. Try again, or email hello@socialectric.com and we will send you the briefing.
Frequently asked questions
- Does the European Accessibility Act apply to charities and nonprofits?
It depends on activity first, then size. The Act covers a closed list of services provided to consumers (Article 2), and the one that catches NGOs is e-commerce: selling goods or services online. Only once a service is on that list does size matter, and a microenterprise providing services (fewer than 10 people, and turnover or balance sheet not over €2 million, Article 3(23)) is exempt. Many established international NGOs run shops, ticketed events or paid training that are in scope. Even exempt organisations face growing accessibility expectations from funders and partners.
- What is EN 301 549 and how does it relate to WCAG?
EN 301 549 is the European digital accessibility standard associated with the EAA. Its V3.2.1 incorporates WCAG 2.1 Level AA as its core technical requirements, so meeting WCAG 2.1 AA gets you most of the way to it. The EAA separately requires a provider whose service is in scope to explain in that service's terms and conditions how the service meets the accessibility requirements (Article 13 and Annex V).
- What are the penalties for EAA non-compliance?
The Act itself sets no figure and no percentage of turnover. Article 30 leaves penalties to each member state, requiring only that they be effective, proportionate and dissuasive, accompanied by remedial action, and set with regard to the seriousness of the non-compliance and the number of people affected. So the answer depends entirely on which member state is enforcing, and each country where you sell an in-scope service can enforce independently.
- Does the EAA apply to UK nonprofits after Brexit?
The EAA does not apply to UK domestic operations. It can apply to a UK-based NGO where that NGO provides one of the Article 2 services to consumers in the EU, which for most NGOs means selling online. Accepting donations from EU donors, delivering programmes in EU countries and serving European audiences are not, on their own, triggers. The UK Equality Act 2010 creates separate domestic accessibility obligations that apply regardless.
- Is WCAG 2.1 or WCAG 2.2 required by the EAA?
WCAG 2.1 AA, via EN 301 549 V3.2.1. That is still the position: EN 301 549 V4.1.1, published in September 2026, is the first version written as a harmonised standard for the EAA and it adopts WCAG 2.2, but it is not yet cited in the Official Journal of the European Union, so it confers no presumption of conformity yet. WCAG 2.2 adds to 2.1 rather than replacing it, so building to 2.2 now avoids a second round of remediation later.
- Do we need an accessibility statement on our website?
The EAA's duty is narrower than it is often described. Where a service is in scope, Annex V requires the provider to set out in the service's general terms and conditions how the service meets the accessibility requirements, and to make that information public in accessible formats. The separate public-sector-style accessibility statement comes from the Web Accessibility Directive, which excludes most NGOs. A published statement is still the clearest way to carry the duty and to answer a UK charity's Equality Act position: see the Accessibility Statement Template for Nonprofit Websites.
- How much does it cost to make a nonprofit website EAA compliant?
For websites built on accessible foundations such as the Lumos framework, remediation costs are modest. For websites built without accessibility consideration, remediation can be extensive enough that rebuilding on an accessible framework is more cost-effective.
- Can we be fined if we are actively working on compliance?
The Directive is built around correction rather than punishment. Article 23 requires member states to follow up complaints and to verify that the operator has taken the necessary corrective action, and Article 30 requires penalties to be accompanied by effective remedial action and to be scaled to the seriousness of the non-compliance. How much latitude that produces in practice is a matter for each national authority. Document your remediation plan, keep records of audits and fixes, and publish what you are doing.
- How does the EAA interact with the UK Equality Act?
They are separate legal frameworks. The Equality Act 2010 makes it unlawful for a service provider to discriminate against a person requiring a service (section 29) and imposes a duty to make reasonable adjustments (section 20), and it applies to a UK charity's website whether or not anything is sold. The EAA applies to the Article 2 services provided to consumers in the EU. An international NGO may need to answer both: see Website Accessibility for Nonprofits for the governance view.
- How often should we audit our website for EAA compliance?
At minimum, annually and after any significant site changes. A quarterly automated scan plus an annual manual audit is a sensible governance cadence. On how that cadence tends to be set up, see Accessibility Fails Because It Is Treated as a Task, Not a Property of the System.