13.10.2025
Website Development & UX/UI

Since 28 June 2025, the transposition of European Directive 2019/882 has imposed accessibility requirements on certain services, including e-commerce. This guide explains who is affected, the exemptions, the RGAA, audits and inspections.

Since 28 June 2025, new accessibility obligations have applied in France to certain products and services, in particular e-commerce websites and applications, banking services and several transport and communication services. They result from European Directive 2019/882, transposed into French law.
This change does not mean that all companies must automatically make all their websites RGAA-compliant. The scope depends on the nature of the services offered, the organisation's status and the exemptions provided for in the texts.
The websites of public bodies and certain private organisations are also subject to a separate accessibility regime, stemming from Article 47 of the Law of 11 February 2005.
Which companies are affected? What obligations apply to an e-commerce site? Which technical criteria need to be checked? And how do you prepare a digital accessibility audit?
ID Interactive is a digital agency based in Arradon, near Vannes (Morbihan), since 2006, and a Google Partner, Meta Business Partner and Shopify Partner. It supports organisations in interface design and website development.
This guide presents the main obligations in force in October 2026 and the steps to plan to improve the accessibility of a digital service.
Digital accessibility means designing websites, applications and digital services that can be accessed and used by people with disabilities.
The situations concerned may relate in particular to visual, hearing, motor, cognitive or neurological impairments.
Accessibility is also useful in many temporary situations: using a keyboard rather than a mouse, difficulty reading a screen in bright sunlight or watching a video without sound.
The international WCAG recommendations (Web Content Accessibility Guidelines) are based on four principles.
These principles provide a foundation for designing accessible interfaces.
They must be applied to pages, but also to forms, menus, documents, videos and integrated services.
28 June 2025 marks the entry into application of new European accessibility requirements covering certain categories of products and services.
The reference European text is Directive (EU) 2019/882 of 17 April 2019, often called the European Accessibility Act.
In France, its transposition relies in particular on Law No. 2023-171 of 9 March 2023 and Decree No. 2023-931 of 9 October 2023.
An order of 9 October 2023 also sets out the requirements applicable to the products and services concerned.
The scheme covers in particular:
The regulations also cover certain products, such as computers, smartphones, e-readers and self-service terminals.
Companies must determine whether their products or services actually fall into these categories before assessing their obligations.
No.
A company showcase website does not automatically fall within the scope of the 2019 directive simply because it is accessible online or because the company exceeds an employee threshold.
The services actually provided need to be examined.
For example, a site presenting a company's business is not necessarily in the same situation as a store allowing consumers to order and pay online.
Other accessibility rules may nevertheless apply depending on the organisation's status or activities.
Yes, the digital services of public-law entities are subject to the accessibility regime provided for by Article 47 of the Law of 11 February 2005.
This obligation existed before 28 June 2025.
The local authority must in particular take into account the RGAA rules, the requirements to publish an accessibility statement and the organisation of its accessibility work.
For a creation or redesign project, ID Interactive's guide to the specifications for a municipal website sets out the main points to anticipate.
The obligations arising from Directive 2019/882 concern operators offering the products and services covered by the texts, subject to the applicable provisions and exemptions.
The size of the company may determine whether a particular exemption is possible for certain service providers.
The French Consumer Code provides an exemption for companies providing services and employing fewer than ten people, where their annual turnover does not exceed two million euros or their balance sheet total does not exceed two million euros, under the conditions laid down in the text.
This definition corresponds to a company size threshold, not to the French tax status of micro-entrepreneur.
A small company may therefore fall under the European notion of microenterprise even if it does not use the micro-business tax regime.
However, simply having fewer than ten employees is not enough to reach a conclusion without examining the other criteria.
Likewise, the exemption applicable to service providers should not be presented as a general exemption for all manufacturers and distributors of products.
A company that does not benefit from the exemption must examine the obligations applicable to its products or services concerned.
However, it does not automatically become subject to all the RGAA obligations for all its sites.
The decisive criterion remains the interplay between the activity concerned, the organisation's status and the applicable legal regime.
The French Consumer Code also provides for cases where certain requirements may be exempted, in particular when they would entail:
These exemptions must be assessed and justified according to the applicable procedure.
They do not amount to a simple statement that the corrections would be too costly.
The companies concerned must also comply with the information and declaration formalities required by their regime.
The RGAA and the obligations applicable since June 2025 should not be confused.
The RGAA is the French standard used to assess the compliance of the digital services of organisations falling within the scope of Article 47 of the 2005 law.
Directive 2019/882, for its part, governs the accessibility of specific categories of products and services.
The two schemes share a common objective, but they do not lay down exactly the same administrative obligations or the same inspection procedures.
The Article 47 scheme concerns in particular:
Particular situations and exceptions must be examined within the appropriate legal framework.
In October 2026, the standard published on the official website is RGAA 4.1.2.
A version 5 is in preparation, with publication announced for the end of 2026.
This planned change does not justify postponing accessibility work.
The organisations concerned must continue to use the standard in force, while anticipating changes in methods and checks.
The WCAG are international recommendations published by the W3C.
WCAG 2.2 was published in October 2023.
They serve as a reference for many accessibility initiatives and are useful for designing digital services that can be used by a wider audience.
The legally applicable level and version must, however, be determined from the relevant texts and standards.
It is not enough to claim that a site complies with WCAG 2.2 to automatically conclude that it meets all French obligations.
An e-commerce site covered by the scheme must make accessible the features and information falling under the applicable requirements.
The work should not stop at the home page.
It must cover the entire purchase journey.
Visitors must be able to understand the categories, access products and use the main navigation functions.
Menus, filters and interactive components must in particular be usable with suitable means of interaction.
Essential information must be presented clearly.
Important images must have relevant text alternatives.
Variations in colour, size or features must not rely solely on a colour code that some people cannot understand.
Add-to-cart, quantity and confirmation buttons must be usable.
Information about products, prices and the order must remain understandable.
Errors must be identifiable and correctable.
The identification methods, security features and payments provided as part of the service must meet the requirements that apply to them.
This involves examining forms, checks, login journeys and payment components.
A store can have an accessible interface while having a checkout funnel that is difficult to use.
For e-commerce, checking the journey all the way to payment is therefore essential.
Applications, modules and components provided by third parties can also create barriers.
Using Shopify, PrestaShop, WordPress or another technology does not, on its own, prove compliance.
The result depends on the theme, developments, integrations and configuration of the service.
To prepare these projects, ID Interactive presents its support on its page dedicated to e-commerce website creation.
The documents and information to be published depend on the applicable regulatory framework.
The Article 47 scheme provides in particular for a compliance assessment and an accessibility statement.
The statement indicates the level of compliance found, the non-accessible content and information useful to users.
The organisations concerned must also organise their accessibility work, in particular with a multi-year plan lasting no more than three years and annual action plans.
The Accessibility page must provide access to the required information.
A compliance statement cannot be written correctly without a real assessment of the service.
Service providers must in particular make information on the compliance of their services available to the public and set up appropriate monitoring procedures.
The documentation and declaration arrangements are not identical to those of the RGAA scheme.
A company subject to e-commerce obligations should therefore not automatically copy the administrative requirements of public bodies without checking its own regime.
It depends on the framework concerned.
For organisations subject to Article 47, the statement is one of the obligations provided for.
For services falling under Directive 2019/882, the professional must comply with its own information, compliance and monitoring obligations.
An RGAA audit report can be useful evidence, but it does not automatically replace all the information required for a service subject to the Consumer Code.
Accessibility must be built into the design of content and interfaces, then checked through testing.
Essential functions must be accessible without using a mouse.
Users must be able to move through links, buttons, menus, forms and interactive windows.
The keyboard focus must be visible.
No area should prevent the user from continuing to navigate with the keyboard.
Important information must remain readable.
Colour contrasts must meet the applicable requirements.
Under WCAG level AA criteria, body text should generally have a contrast ratio of at least 4.5:1, subject to the exceptions provided for.
The minimum contrast required differs for large text and certain interface components.
Readability must also be checked when the user enlarges the text or changes the display.
An image essential to understanding must have an appropriate alternative.
This does not mean mechanically repeating its file name or title.
For example, an image showing the different stages of a process may require a description of the information conveyed.
Conversely, a purely decorative image can be ignored by assistive technologies when it is correctly marked up.
Headings must reflect the organisation of the content.
Lists must use appropriate markup and tables must be reserved for genuine tabular data.
Buttons must be used for actions, and links for navigation.
This structure helps people using screen readers and makes interfaces more robust.
Each field must be labelled.
Required information must be clearly indicated.
When an error occurs, the user must be able to understand what needs to be corrected.
Messages must not be conveyed by colour alone.
Depending on the nature of the media and the applicable criteria, it may be necessary to provide subtitles, transcripts and appropriate alternatives.
These elements must be built into the project's requirements from the design stage.
Drop-down menus, accordions, modal windows, calendars, carousels and booking interfaces require particular attention.
A component that works with a mouse may remain unusable with a keyboard or a screen reader.
Tests must cover its real behaviour, not just its appearance.
An accessibility audit combines technical checks and manual verification on the relevant pages and journeys.
It cannot be reduced to an automated score.
Identify the site or service to be audited and the applicable rules.
Select a representative sample of pages and journeys.
For an e-commerce site, the sample may include in particular:
Automated tools can detect certain errors: images without alternatives, insufficient contrast or structural problems.
However, they cannot fully assess a service's accessibility.
The checks should include in particular:
Where relevant, user tests involving people with disabilities also provide significant value.
Each issue must be traceable to the page or component concerned.
The report must distinguish the applicable criteria, the problems found, their impact and the recommended corrections.
Documentation obligations depend on the legal regime concerned.
After corrections, a new check makes it possible to verify that the problems have actually been resolved.
You also need to make sure the changes have not introduced new malfunctions.
Compliance must then be monitored as the site evolves.
Penalties and competent authorities depend on the applicable legal scheme.
The DGCCRF (French consumer protection authority) is one of the authorities competent to check the obligations laid down in the Consumer Code.
Depending on the area, it works in coordination with other authorities.
Inspections may lead to compliance orders and other measures provided for in the texts.
The offences concerned may in particular be punished by fines of 7,500 euros, which can be cumulated according to the number of offences found, under the applicable conditions.
Inspection falls under a separate regime, including powers entrusted to Arcom (the French audiovisual and digital communication regulator).
The penalties should not be confused with those for products and services covered by the Consumer Code.
Certain transitional periods are provided for in the texts.
They concern in particular certain products used to provide services and certain contracts concluded before 28 June 2025.
However, these provisions do not amount to a general postponement of the accessibility obligation for existing e-commerce websites and applications.
The service's situation must be examined precisely before invoking a transitional period.
Accessibility and SEO have things in common, in particular the quality of HTML markup, content structure and clarity of links.
These good practices make content easier for users to consult and can help make information more understandable for crawlers.
However, achieving a good accessibility score or carrying out an RGAA audit does not guarantee a better position on Google.
Accessibility, editorial relevance and search engine rankings must be measured separately.
SEO also involves content, indexing, architecture and visibility issues.
ID Interactive supports these issues through its services in SEO.
A clear semantic structure and accessible information can make it easier for search systems to use certain content.
But RGAA or WCAG compliance is no guarantee of being cited by ChatGPT, Gemini, Perplexity or Google AI Overviews.
GEO must be assessed according to the mentions, cited sources and recommendations actually observed.
Accessibility should therefore not be presented as a technique that on its own will earn more AI citations.
Accessibility generally requires less corrective effort when it is anticipated at the design stage rather than added after development.
The process starts with the very first decisions:
An interface can be technically well built, then become difficult to use because of poorly written content, an image without an alternative or an inaccessible PDF document.
Editorial teams and the people responsible for administering the site therefore need to know the good practices relevant to their work.
Not necessarily.
WordPress, Shopify, PrestaShop, Payload CMS and other solutions can produce sites whose accessibility depends heavily on the quality of the theme, developments, components and content.
Changing CMS is not, on its own, a compliance solution.
You first need to identify the problems, their causes and the corrections required.
The UX/UI design approach of ID Interactive can build these requirements in from the creation of the interfaces.
ID Interactive develops bespoke websites and web applications.
Accessibility can be addressed during a creation, a redesign or work on an existing site.
Depending on the contracted scope, support may include:
1. Initial analysis. Identify the main journeys, navigation difficulties and components to examine.
2. Technical scoping. Define the objectives and requirements applicable to the project.
3. UX/UI design. Design interfaces that are easy to use with different navigation methods.
4. Technical corrections. Adapt components, forms, HTML structures and interactive behaviour.
5. Acceptance testing. Check that the journeys work and carry out the planned tests.
6. Editorial support. Make contributors aware of the practices that keep content accessible.
7. Follow-up. Plan the necessary checks as the site evolves.
Carrying out a formal audit, drawing up an accessibility statement and legally validating compliance must be explicitly defined according to the requirements and skills involved.
No full compliance should be promised without analysing the scope and checking the results.
Preparing to create or redesign a website? See ID Interactive's website creation services to explore suitable technical solutions.
This checklist is a basis for preparation, not a full compliance audit.
Since 28 June 2025, new obligations have applied to certain services and products, in particular e-commerce and several essential consumer services.
These obligations are in addition to the older scheme applicable to public bodies and certain private organisations, in particular under the RGAA.
You therefore need to start by identifying the legal regime that actually applies to your organisation.
The size of the company, the nature of the service and any exemptions must then be examined.
On the technical side, the priority is to make content perceivable, features operable, information understandable and interfaces compatible with assistive technologies.
Digital accessibility must be built into the design, checked during acceptance testing and monitored throughout the life of the site.
L’European Accessibility Act est le nom couramment donné à la directive (UE) 2019/882 du 17 avril 2019, relative aux exigences d’accessibilité applicables aux produits et services. Ses exigences s’appliquent depuis le 28 juin 2025. En France, sa transposition repose notamment sur la loi n° 2023-171 du 9 mars 2023 et sur le décret n° 2023-931 du 9 octobre 2023.
Le RGAA, ou Référentiel général d’amélioration de l’accessibilité, est le référentiel français utilisé pour évaluer la conformité des services numériques des organismes relevant de l’article 47 de la loi du 11 février 2005. En octobre 2026, la version publiée sur le site officiel est la 4.1.2 ; une version 5 est en préparation.
Non. Les outils automatiques détectent certaines erreurs, comme des images sans alternative, des contrastes insuffisants ou des problèmes de structure, mais ne permettent pas d’évaluer intégralement l’accessibilité. Un audit y ajoute des tests manuels : navigation au clavier, lecteur d’écran, formulaires, messages d’erreur et parcours essentiels, sur un échantillon représentatif de pages.
Selon le critère WCAG de niveau AA, un texte courant doit généralement présenter un rapport de contraste d’au moins 4,5:1, sous réserve des exceptions prévues. Le seuil est de 3:1 pour le texte de grande taille. Le contraste requis diffère aussi pour certains composants d’interface, et la lisibilité doit être vérifiée lorsque l’utilisateur agrandit les caractères.
Non. Le recours à Shopify, PrestaShop, WordPress ou une autre technologie ne constitue pas, à lui seul, une preuve de conformité. Le résultat dépend du thème, des développements, des intégrations et de la configuration du service. Les applications, modules et composants fournis par des tiers peuvent aussi créer des obstacles, notamment dans le parcours de commande.