The European Accessibility Act has applied to e-commerce, banking, passenger transport and e-book services since 28 June 2025. Enforcement started slowly: Germany's joint market surveillance body for accessibility, the MLBF, only began operating on 26 September 2025. That adjustment period is closing, and the most common fallback plan we see is the weakest one, a vague intention to claim "disproportionate burden" if anyone asks.
Disproportionate burden is a real provision, not a loophole, and it is evidentiary. Article 14 of the Directive turns it into three things: a documented cost assessment against the criteria in Annex VI, a notification to your market surveillance authority, and a five-year review clock. By the end of this guide you will know what evidence that file needs, how to run the three Annex VI ratios, which facts disqualify the claim outright, and how to notify without over-disclosing.
What the EAA lets you claim, and what it does not
Article 14(1) sets two separate escape routes, and people conflate them. Fundamental alteration means compliance would significantly change the basic nature of the product or service. That is an argument about what your service is. Disproportionate burden is an argument about numbers. Different evidence, different file.
Two limits matter before you spend time on either. Recital 66 states that lack of priority, time or knowledge is not a legitimate reason, so "we had a roadmap freeze" is not a claim. And Article 14(6) removes the ground entirely if you received funding, public or private, from outside your own resources, for improving accessibility.
Step 1: Scope the claim to one service, not your whole estate
Article 14(5) requires service providers to renew the assessment "for each category or type of service". That cuts both ways: a recurring obligation, but also permission to be narrow. A claim scoped to "our website" is harder to defend and to maintain than one scoped to the legacy returns portal you are decommissioning.
Write the scope statement first, in one sentence, naming the service, the interface, the requirement you cannot meet, and the EN 301 549 clause it maps to. If you cannot write that sentence, you are not ready to claim. You are still doing an audit.
Step 2: Price the work in the two cost buckets Annex VI names
Annex VI does not accept a blended number. It splits the net cost of compliance in two, and your file should keep them separate, because that is how an authority reads it.
One-off organisational costs: accessibility staff, training, developing a process to include accessibility, guidance material, and the cost of understanding the legislation.
Ongoing production and development costs: designing the accessibility features, changes to production processes, testing, and documentation.
These are net costs: subtract work you would have done anyway in the same period. A design system rebuild already in the backlog is not an accessibility cost. Get the estimates from the engineers who would do the work, in writing, with a date. An estimate traceable to a named person beats a confident total.
Step 3: Run the three Annex VI ratios and write down the numbers
Present all three criteria. A file that answers only the flattering one invites a follow-up question.
| Annex VI criterion | What you compute | Where the denominator comes from |
|---|---|---|
| Ratio to overall costs | Net compliance cost ÷ operating and capital expenditure of providing that service | Service-level cost allocation, same period as the estimate |
| Costs and benefits versus benefit to users | Operator cost and benefit set against the estimated benefit for persons with disabilities, factoring in how much and how often the service is used | Usage analytics for that service, plus disability prevalence data for your market |
| Ratio to net turnover | Net compliance cost ÷ net turnover of the economic operator | Filed statutory accounts, not management figures |
There is no numeric threshold in Annex VI. No percentage makes a burden automatically disproportionate. Article 14(7) empowers the Commission to adopt delegated acts supplementing Annex VI (the first was due by 28 June 2020 and applies at the earliest from 28 June 2025), so check whether one is in force on your assessment date. With no threshold, the file persuades by being checkable, not by the ratio being large.
Worked example (illustrative figures only)
A retailer runs a 14-year-old in-store pickup kiosk alongside its main site. The kiosk handles roughly 0.4% of orders and is due for replacement in 18 months. Rebuilding it to the relevant EN 301 549 clauses is small against group turnover but large against that service's own cost base, with low usage frequency: the shape Annex VI's second criterion is built to weigh. The same spend against the main checkout would fail the same test. These figures are illustrative, not a benchmark. [INTERNAL DATA NEEDED: real cost ranges and service-level usage splits from Switas audit engagements, to replace the illustrative example.]
Step 4: Check the disqualifiers before you file
Run this list before anyone writes a notification. A yes in the first three rows ends the claim.
- Did you receive external funding, public or private, for improving accessibility of this service? (Article 14(6): claim unavailable.)
- Is the real reason priority, time or knowledge? (Recital 66: not legitimate.)
- Are you a microenterprise providing services? (Article 4(5): exempt, no claim needed.)
- Is the requirement you are avoiding a cheap, well-understood fix such as a text alternative, a label or a contrast value? Those make the rest of the file look like avoidance.
- Is the assessment dated, with a named author?
- Can you produce the estimates, the cost allocation and the statutory turnover figure in one place, on request?
Step 5: Notify the right authority, in the right format
Article 14(8) requires operators relying on paragraph 1 to notify the relevant authority in each member state where the service is provided. This is separate from the Article 13(4) notification of non-compliance; do not merge them. Recital 68 sets the disclosure posture: inform the authority that you are relying on the provision, and supply the assessment only on request.
Format varies by country, and this is where multi-market operators lose time. As of early 2026, standardised notification forms existed in Austria, Luxembourg, the Netherlands (e-commerce and e-books) and Sweden (e-commerce), while Germany accepted notifications through ordinary contact channels. Some member states split market surveillance across several authorities by service type, so "the regulator" may be two or three bodies. Build the country list first.
Step 6: Set the five-year clock and the re-assessment triggers
Article 14(3) requires you to keep the assessment for five years from the last provision of the service. Article 14(5) requires service providers to renew it when the service is altered, when an authority requests it, and at least every five years regardless.
Put all three triggers where your team already looks: a calendar entry five years out, a line in that service's release checklist asking whether the change alters the basis of the assessment, and a named owner. A claim that was defensible in 2026 and survived two replatforms untouched is a stale document with your signature on it.
Where this breaks down
This process does not tell you whether your claim will be accepted. Annex VI has no threshold, member states transposed the Directive with real differences (accessibility statement requirements differ between Germany, France and Spain), and published decisions on burden claims remain scarce. Anyone offering a pass/fail percentage is inventing it.
It also does not cover the standard moving under you. EN 301 549 V4.1.1 was adopted by the European standards organisations on 24 August 2026 and published on 2 September 2026, aligning with WCAG 2.2 Level A and AA where V3.2.1 referenced WCAG 2.1. The presumption of conformity attaches only once a version is cited in the Official Journal, so record which version you tested against, and when.
Finally, it is EU-specific. Turkey's regime is a separate obligation with no comparable exemption. The Presidential circular on the accessibility of websites and mobile applications, published in the Official Gazette on 21 June 2025, binds public institutions, banks, private hospitals and schools, transport operators, licensed travel agencies and e-commerce providers under Law No. 6563. The baseline is WCAG 2.2 Level A, and the e-commerce compliance date is 20 June 2027. A Turkish retailer selling into the EU can be an economic operator under the EAA and covered by the circular, and an EU burden file does nothing for the Turkish deadline.
FAQ
Does a disproportionate burden claim make my service compliant?
No. It limits how far the requirements apply to the service you scoped, on the basis you documented. Everything outside that scope stays fully in scope.
Do I have to publish the assessment?
No. Under Recital 68 you inform the authority that you rely on the provision and provide a copy on request. Accessibility statement duties are separate, and several member states require those to disclose inaccessible parts and alternatives.
What counts as a "category or type of service"?
The Directive does not define it. Scope by the unit a user would recognise and a regulator could inspect, such as a booking flow, a kiosk interface or an e-book reader app, rather than by internal team boundaries.
Are microenterprises in scope?
Under Article 4(5), microenterprises providing services are exempt from the accessibility requirements altogether, so no claim is needed. Microenterprises dealing with products need not document the assessment under Article 14(4) but must supply the relevant facts on request. The test applies to the entity providing the service, not the brand.
Can a large company claim disproportionate burden?
Nothing in Article 14 excludes it, but the third criterion compares cost to net turnover, so the arithmetic gets harder as turnover grows. Large operators more often have a defensible claim on a legacy surface than on a core journey.
What happens if we never notify?
You lose the benefit of the provision. An undocumented, unnotified claim looks identical to plain non-compliance. The first year of enforcement suggests authorities ask for a remediation plan, which is far easier to answer with a file than without one.
Next step
Pick your weakest service, write the one-sentence scope statement from Step 1, and see whether you can fill the three rows of the Annex VI table from documents you already have. If you can, you have a claim worth building. If you cannot, you have an audit to run first, and that is what we do: request an EAA and EN 301 549 readiness audit from Switas.
Sources
- Directive (EU) 2019/882, European Accessibility Act (full text)
- European Commission, European Accessibility Act
- Covington, Global Policy Watch (application date)
- Taylor Wessing (notification forms, MLBF, enforcement)
- Davis Wright Tremaine (EN 301 549 V4.1.1 dates)
- ETSI, EN 301 549 V4.1.0 draft
- Türkiye, Ministry of Family and Social Services (Presidential circular)
- KPMG Türkiye (covered entities, 2026 and 2027 dates)







