A French court ordered Carrefour to make its app accessible
Published
On 4 June 2026 a French court ordered Carrefour to make its website and its mobile app fully accessible within six months. It is the first order under the European Accessibility Act to name a mobile app. What was decided, what comes next, and what it changes for a Flutter team.
What the court decided
Two associations, apiDV and Droit Pluriel, supported by the legal collective Intérêt à agir, took Carrefour France to the tribunal judiciaire de Caen. On 4 June 2026 the court ordered Carrefour to make carrefour.fr and the Carrefour mobile app fully accessible to people with disabilities within six months, with a penalty of 500 € for every day it runs late after that.
Carrefour argued that it had reached 71% conformity with the RGAA, the French accessibility method. The court did not accept a share: an e-commerce site cannot be only somewhat accessible, it has to be accessible in full.
The legal basis was article L412-13 of the French Code de la consommation, which is how France carries the European Accessibility Act into national law.
What came before, and what is next
In July 2025, days after the Act took effect, the associations sent formal notices to four supermarket chains: Auchan, Carrefour, E.Leclerc and Picard.
The first case decided went the other way. On 5 May 2026 the court in Lille dismissed the claim against Auchan: it read the law as keeping France's older regime, with its threshold of 250 M€ in turnover, and the Auchan subsidiary fell below it. The associations have appealed.
Carrefour has said it is examining the decision and reserves the right to appeal. E.Leclerc is due to be heard on 22 September 2026 in Créteil. A hearing is not a ruling; when the decision comes, we will add it here. Picard has no hearing date yet.
Outside France, the Dutch consumer authority ACM has sent information requests to e-commerce operators, including companies with no office in the EU, and formal enforcement is expected in the second half of 2026.
What it changes for a Flutter app
The app is in the order by name. A retailer cannot treat its website as the accessible channel and the app as something else.
A percentage did not help. Automated checks find part of the problems; whether a blind customer can place an order with TalkBack or VoiceOver is found by a person going through it, on both platforms.
What such gaps look like in a Flutter app: in our sample audit of Wonderous, eight screens gave 161 occurrences in 33 places in the code: touch targets smaller than 24×24 (83 occurrences), text with too little contrast (35), controls sharing one label (22) and controls a keyboard cannot reach (13). Each one comes with a file and a line.
None of this says how the court in Créteil will decide, or that any given app will end up in court. It does mean that “mostly accessible” is not an answer to give a lawyer. If you are not sure the Act reaches your app, seven questions tell you in a minute; if it does, the accessibility audit checks both platforms.
Sources
Not legal advice. Written from the published reports listed below, checked on 17 September 2026.