Regulation

Formal notice for digital accessibility non-compliance: responding in 5 steps

A formal notice for digital accessibility non-compliance requires a swift, factual, and documented response. It is essential to meet deadlines, assess gaps, implement corrections, and have the legal strategy validated by a lawyer.

Figures, methodology and reuse terms: see the citable data →

The short answer

When faced with a formal notice regarding digital accessibility, acknowledge receipt without prematurely admitting fault, retain all documents, and identify the specified deadline. Have the affected service analyzed, establish a dated correction plan, and respond point-by-point with verifiable evidence. Quickly involve legal, product, and technical teams. A lawyer must assess the demands, the applicable procedure, and the risks specific to the case.

The immediate goal is not to promise instant compliance but to regain control of the file. A credible response relies on three complementary elements: cautious legal qualification, a traceable technical diagnosis, and a realistic remediation timeline. Every statement addressed to the issuer of the formal notice must be linkable to a document, a test, or a documented internal decision.

1. Qualifying the formal notice and its author

What it is, and what it is not

A formal notice is a formal request to fulfill an obligation or to cease an alleged breach. It does not, in itself, constitute a conviction. However, it may prepare the ground for an administrative claim, legal action, or a request for compensation.

Identify the actual author, their authority to act, the legal basis invoked, and the scope concerned. A public authority may intervene within the limits of its competences. An association, a competitor, or a mandated firm may also send a request, but the admissibility of any subsequent action depends on the legal basis and the standing to act.

Also examine the precision of the grievances. Does the letter target an entire website, a mobile application, a customer area, or specific pages? Does it mention concrete obstacles, criteria from a reference framework, an accessibility statement, or a publication obligation? This delimitation is essential: it determines the checks to be carried out and avoids responding to reproaches broader than those actually formulated.

Upon receipt, create a single file containing the original letter, attachments, prior correspondence, available versions of the service, and relevant public documents. Appoint a coordination officer to ensure that teams do not respond separately to the sender and that technical findings remain consistent with the legal position.

• Keep the letter, its annexes, and proof of receipt
• Note the deadline, the cited texts, and the pages concerned
• Verify the identity and any mandate of the sender
• Forward the file to a lawyer for the specific case

2. Secure the deadline without responding in haste

There is no single deadline applicable to all formal notices. The deadline may come from the letter itself, a specific regulation, a decision, or an ongoing procedure. It must therefore be treated as a legal matter to verify, rather than a mere internal deadline.

Promptly send a concise acknowledgment of receipt. It may confirm that the matter is being handled, request any missing documents, and state that an analysis is underway. Avoid making any general admission of non-compliance before establishing the facts and obtaining legal advice.

The acknowledgment of receipt should not become an improvised response on the merits. It may precisely state the date of receipt, identify the department under review, and designate a single point of contact. If the deadline appears incompatible with conducting a thorough review, a lawyer may assess whether to request an extension, explaining the steps already taken.

Simultaneously, build a reverse timeline. Allocate time for the audit, assessing findings, validating corrections, gathering evidence, and legal proofreading. A last-minute fix that has not been tested may introduce new issues or contradict statements made in the response.

3. Conducting a benchmark that can be used to counter approximations

Combining automation and human checks

An automated scan can quickly identify some of the detectable flaws and classify them by severity. However, it is not sufficient to demonstrate full compliance, as certain criteria require human assessment, keyboard navigation, or testing with assistive technologies.

An initial Inclaria scan can provide an objective benchmark and a prioritised correction plan to be attached to the response as proof of due diligence. The scope, date, tested pages, rules used, and limitations of the analysis must remain explicit.

The Inclaria 2026 study shows that 94.5% of the 55 e-commerce sites analysed in the French panel exhibit at least one critical or serious non-conformity. This finding describes this precise scope and does not allow for assumptions about the situation of a particular site.

To make the benchmark usable, retain the scan parameters, tested URLs, environment used, and service version. Results must be reviewed to eliminate false positives, confirm flaws, and identify obstacles that automation does not detect. Two analyses conducted on different scopes cannot be compared without caution.

Human checks must prioritise the essential user journeys mentioned in the formal notice: keyboard navigation, form comprehension, error message rendering, content access, identification of interactive components, and use with relevant assistive technologies. Each confirmed anomaly should be reproduced following a brief and consistent protocol, with the expected result and the observed result.

The audit should not be solely focused on defending the case. A vague complaint may reveal a real obstacle different from the one described by the sender. Documenting this finding honestly allows for the correct correction to be implemented and presents a more robust response than a purely formal challenge.

4. Building a dated and verifiable correction plan

The plan must link each grievance to a finding, an action, a responsible party, a deadline, and expected evidence. Prioritise blockages that prevent access to an essential function, followed by serious defects and structural corrections.

• Describe the audited scope and the methods used
• Associate each confirmed defect with a corrective measure
• Plan for verification after correction
• Archive tickets, screenshots, reports, and meeting minutes
• Distinguish between delivered corrections and those still planned

If the organisation refers to the RGAA, a full compliance declaration requires adherence to all applicable criteria. A favourable overall score does not, therefore, negate a non-compliant criterion. The applicability of the RGAA or another framework must be assessed based on the service and the relevant legal regime.

A credible timeline accounts for real dependencies: modification of the design system, intervention by a service provider, correction of a third-party component, functional testing, or validation of a new version. If a deadline depends on an external actor, indicate this dependency without turning an uncertain date into a firm commitment.

For each delivered action, retain evidence before and after correction, as well as the result of the non-regression check. A screenshot may illustrate a change, but it does not always demonstrate functionality with a keyboard or screen reader. Evidence must therefore be adapted to the nature of the defect addressed.

Some structural corrections require more time than a one-off adjustment. In such cases, the plan may distinguish between immediate measures to reduce the obstacle, the definitive correction, and checks to prevent its reoccurrence. This distinction enhances transparency without presenting a temporary measure as achieved compliance.

5. Addressing each point with evidence

The response must address each request directly. For each point, state whether it is confirmed, contested, or under verification, then attach the available evidence. A general promise of correction is less convincing than a realistic timeline accompanied by already verified deliveries.

The order issued by the Caen District Court on June 4, 2026, in the case opposing apiDV and Droit Pluriel against Carrefour, gained media attention for mandating accessibility compliance with a penalty and a six-month deadline. Its exact scope, procedural status, and applicability to another company must be analyzed by a lawyer based on the full decision.

Adopt a consistent structure: summary of the grievance, verification result, adopted position, action taken, deadline, and supporting document. When a point is contested, briefly explain the facts or the limitations of the sender’s methodology. Avoid aggressive wording, assumptions about their intentions, or technical assertions that cannot be reproduced.

Annexes must be identified and referenced in the body of the response. A voluminous report submitted without explanation may obscure the relevant elements. A short summary can indicate what was tested, what has already been corrected, what remains planned, and what additional verifications are foreseen.

Before sending, ensure consistency between the letter, the correction plan, internal tickets, and the actual state of the service. A response announcing an un-deployed correction or a deadline contradicted by internal planning may weaken the entire case. The lawyer must validate the final wording and decide which documents are appropriate to disclose.

6. Avoid responses that worsen the case

Ignoring the letter allows the other party to set the timeline and narrative of the facts alone. Promising full compliance without an audit, quietly removing a statement, or producing an automated score as the sole evidence also weakens the response.

• Do not alter received evidence or the history of exchanges
• Do not downplay an obstacle preventing an essential user journey
• Do not commit to an impossible deadline
• Do not confuse technical fixes with legal validation
• Do not publish a commitment that has not been approved by the relevant stakeholders

Also avoid limiting the intervention to a series of isolated fixes if the issue stems from a shared component or a flawed publication process. A lasting solution may require evolving the design system, acceptance testing, approval criteria, and raising awareness among those who produce content.

External communication must remain coordinated. A legal response, an accessibility statement, and a customer service message should not present contradictory compliance statuses. Any public update must reflect the checks actually carried out and clearly distinguish future commitments from corrections already validated.

After sending the response, continue monitoring the plan and keep records of each delivery. The response to the formal notice does not necessarily close the matter: the sender may request clarifications, challenge the measures, or re-examine the service. Continuous traceability then allows for a quick response without reconstructing the file under pressure.

This content is for informational purposes only and does not constitute legal advice. A lawyer specialising in digital law should review the formal notice, the applicable regulations, the quality of the sender, and the response before it is sent.