Contents
In France, digital accessibility is mandatory for public bodies, companies with at least €250 million in revenue (websites, intranets, apps) and, since June 28, 2025, certain consumer services such as online retail under the European Accessibility Act. Elsewhere, it is an inexpensive best practice if planned early.
Digital accessibility means making a website or app usable by everyone, including people who navigate with a keyboard, a screen reader or a magnifier, or who have trouble telling colors apart. Since June 2025, the topic is no longer limited to the public sector. Here is who is actually required to comply, what the texts say as of October 2026 (with a focus on France, where I am based), and what I recommend building into a business tool. This page is factual and points to official sources: it does not replace advice from a lawyer.
Who is required to comply, as of October 2026
Two regimes apply side by side in France.
Article 47 of the French law of February 11, 2005, amended in 2023, applies to public bodies, to some private organizations performing a public service mission and to companies with revenue of at least €250 million (average revenue generated in France over the last three closed financial years). According to the official French digital accessibility site (in French), it covers websites, intranets and extranets, software used through a browser or mobile app, and mobile apps.
The European Accessibility Act (Directive (EU) 2019/882) has applied since June 28, 2025 across the EU. It targets products and services for consumers. The DGCCRF guidance (in French) lists e-commerce, consumer banking, some transport services, telephony and e-books, among others. Service providers with fewer than 10 employees and under €2 million in revenue or balance sheet total are exempt.
The latest change: Decree no. 2026-816 of August 24, 2026 amends the 2019 decree on the accessibility of online public communication services to align it with the European directive’s timeline (sources checked in October 2026).
| Your situation | Applicable text | What it means |
|---|---|---|
| Public body or public service mission | Article 47, 2005 law | RGAA compliance, accessibility statement, multi-year plan |
| Company with at least €250 million revenue in France | Article 47, 2005 law | Same, including intranets, extranets and apps |
| Company selling online to consumers (not a micro-enterprise) | European Accessibility Act | Accessible service, published compliance information |
| Company below €250 million, internal or B2B tool | Usually no direct legal obligation | Best practice, to be checked with a lawyer |
The technical references
The RGAA is France’s official verification method. The current version is 4.1.2; the official site announces version 5 for the end of 2026. At European level, the DGCCRF cites the EN 301 549 standard and the international WCAG 2.1 guidelines as references.
For an organization that is required to comply, compliance must be demonstrated: an audit against the RGAA, a published accessibility statement, and a multi-year accessibility plan. A formal compliance audit should go to a specialist accessibility auditor; my role is to design and build the tool so that it passes that audit without being reworked.
The best practices I build into a business tool
Even without an obligation, an accessible app is easier for everyone to use: a sales rep on a tablet in bright sunlight, a warehouse operator working from the keyboard, an employee whose eyesight changes over the years. The points I put into the requirements:
- Full keyboard navigation, with a visible marker on the active element.
- Sufficient contrast, and information never carried by color alone (a “late” status also has a label).
- Labeled forms and explicit error messages placed next to the field concerned.
- A structure screen readers can follow: ordered headings, named buttons, tables with headers.
- Text that can be enlarged without breaking the layout, and tap targets large enough on mobile.
- No unnecessary time limits, and animations that can be turned off.
These rules cost little when they are set at the mockup stage. They cost a lot when added to a finished app, because they touch every screen.
What it costs
There is no separate “accessibility” line in my pricing: the target level is set during scoping and reflected in the quote.
| Project | Price reference | Timeline |
|---|---|---|
| Focused business app with accessibility best practices built in | $6,800 to $22,400 (€6,000–€20,000)excl. VAT | 1 to 3 months |
| Client portal (client area module: $2,800 (€2,500)excl. VAT in the estimator) | Within the same range depending on scope | 1 to 3 months |
| Formal RGAA compliance required (covered organization) | Quoted separately, with an audit by a specialist | Defined during scoping |
To size your project, the estimator gives you a range in one minute. If you are planning a portal for your clients, the page on client portal cost breaks down the line items.
When it is not the priority
I would rather be honest: for an internal tool used by eight people in a company below the legal threshold, aiming for full RGAA compliance would be out of proportion. The basic best practices are enough, and they are part of any well-designed interface. Likewise, if you use off-the-shelf software, accessibility depends on the vendor: ask for its accessibility statement or conformance report rather than starting a development project.
The picture changes if you are above €250 million in revenue, sell online to consumers, bid on public contracts, or have an employee with a disability who needs to use the tool every day.
Where to start
- Check whether you are covered by either regime, with your lawyer if needed.
- Take stock of your websites, portals and apps, separating public, client-facing and internal tools.
- For a new tool, write accessibility requirements into the requirements document from the start.
- For an existing app, begin with a technical assessment; the audit gives you a costed action plan, to be complemented by an RGAA audit if you are a covered organization.
Frequently asked questions
Is my internal app covered if my revenue is below €250 million?
As a rule, Article 47 of France’s 2005 disability law does not apply to a private company below that threshold, unless it performs a public service mission. The European Accessibility Act targets services for consumers. A purely internal tool therefore often falls outside the obligation, but check your situation with a lawyer.
What is the RGAA?
The RGAA is France’s official method for checking whether a website or app is accessible. The current version is 4.1.2; the official site says version 5 is being drafted for release at the end of 2026, and stresses that this is no reason to pause accessibility work.
Are small businesses exempt from the European Accessibility Act?
According to France’s consumer protection authority (DGCCRF), service providers with fewer than 10 employees and annual revenue or a balance sheet total below €2 million have no accessibility obligation under this law. Above that, a company selling online to consumers is covered.
What are the penalties for non-compliance?
For services covered by the European Accessibility Act in France, the DGCCRF can order compliance and issue fines of €7,500 per offense, which can be cumulative. Article 47 of the 2005 law has its own financial penalties; ask a lawyer to confirm the amounts that apply to you. Other EU countries set their own penalties.