Why 2025 Is the Year Web Accessibility Becomes Non-Negotiable

For years, web accessibility was treated as a nice-to-have — something that mattered mostly to public-sector websites and large corporations. That era is officially over.

On June 28, 2025, the European Accessibility Act (EAA), transposed into French law through updated provisions of the Code de la consommation and reinforced by the existing RGAA 4.1 framework, extends mandatory digital accessibility requirements to a massive swath of private-sector businesses. E-commerce stores, online banking platforms, transport booking systems, telecommunications services — if your business sells to European consumers online, you are very likely affected.

And here’s what catches most small business owners off guard: there is no blanket exemption for being small.

This guide walks you through everything you need to understand — the legal landscape, the technical requirements, the practical steps — so you can move from confusion to compliance without burning through your entire IT budget.

The European Accessibility Act (Directive 2019/882)

Adopted in 2019, the EAA is a European Union directive that harmonizes accessibility requirements across member states. It covers:

  • E-commerce websites and mobile apps
  • Online banking and financial services
  • Electronic communications (VoIP, messaging)
  • Transport services (air, bus, rail, waterborne)
  • E-books and dedicated reading software
  • Operating systems and hardware (computers, smartphones, ATMs, ticketing machines)

Each EU member state was required to transpose the directive into national law by June 28, 2022, and enforcement begins June 28, 2025.

In France, this means the existing RGAA framework — already mandatory for public bodies since 2012 — now extends its practical relevance to private businesses covered by the EAA.

RGAA 4.1: The French Compliance Rulebook

The Référentiel Général d’Amélioration de l’Accessibilité (RGAA) version 4.1 is maintained by the DINUM (Direction Interministérielle du Numérique). It translates the international WCAG 2.1 Level AA guidelines into 106 testable criteria organized across 13 thematic areas.

Think of it this way:

  • WCAG 2.1 = the international standard (published by the W3C)
  • EN 301 549 = the European harmonized standard referencing WCAG
  • RGAA 4.1 = the French operational framework that tells you exactly what to test and how

If your website passes an RGAA audit, it is by definition WCAG 2.1 AA compliant.

Who Exactly Must Comply?

Here is a simplified breakdown:

Business TypeAlready Mandatory?Mandatory from June 2025?
Government websites✅ Yes (since 2012)✅ Yes
Public institutions✅ Yes✅ Yes
Large private companies (250+ employees) providing covered servicesPartially✅ Yes
SMEs providing covered services (e-commerce, banking, telecom, transport)❌ No✅ Yes
Micro-enterprises (<10 employees, <€2M turnover)❌ No⚠️ Conditional exemption possible

Key point: The exemption for micro-enterprises is not automatic. You must formally demonstrate that compliance would represent a “disproportionate burden” — and even then, you are expected to comply as much as reasonably possible and document your efforts.

The Real-World Cost of Non-Compliance

Let’s talk numbers, because nothing motivates action quite like potential fines.

In France, the enforcement mechanism is handled by the ARCOM (Autorité de régulation de la communication audiovisuelle et numérique) and the DGCCRF (Direction générale de la concurrence, de la consommation et de la répression des fraudes). Penalties include:

  • Up to €50,000 per infringement for failure to comply with accessibility obligations
  • Mandatory corrective action orders with deadlines
  • Public naming — your non-compliance can be made public, a reputational blow that is arguably worse than the fine itself

Beyond penalties, consider the business case:

  • Over 12 million people in France live with a disability (source: INSEE). That is roughly 18% of the population.
  • Globally, people with disabilities control an estimated $13 trillion in annual disposable income (source: Return on Disability Group).
  • An accessible website also benefits elderly users, people with temporary injuries, users on slow connections, and — critically — search engines. Accessible sites consistently rank better because the same practices that help screen readers help Googlebot.

Ignoring accessibility is not just legally risky. It is leaving money on the table.

The 13 Thematic Areas of RGAA 4.1

RGAA organizes its 106 criteria into 13 themes. Here is a concise overview of each:

  1. Images — Every informative image must have a relevant text alternative. Decorative images must be ignored by assistive technologies.
  2. Frames — Inline frames (<iframe>) must have accessible titles.
  3. Colors — Information must never be conveyed by color alone. Contrast ratios must meet minimum thresholds (4.5:1 for normal text, 3:1 for large text).
  4. Multimedia — Videos must have captions. Audio content must have transcripts.
  5. Tables — Data tables must have proper headers (<th>) and summaries.
  6. Links — Link text must be explicit. “Click here” is not acceptable.
  7. Scripts — JavaScript components must be keyboard-operable and compatible with assistive technologies.
  8. Mandatory elements — Pages must have valid lang attributes, unique titles, and valid HTML.
  9. Information structure — Content must use proper heading hierarchy, lists, and landmark regions.
  10. Presentation of information — Layout must be achieved with CSS, not tables. Text must be resizable to 200% without loss of content.
  11. Forms — Every form field must have an associated label. Error messages must be explicit.
  12. Navigation — Sites must offer at least two navigation methods (menu + sitemap, or menu + search). Focus order must be logical.
  13. Consultation — Documents must be accessible. Time limits must be controllable. No content should flash more than 3 times per second.

A Practical Compliance Checklist for Small Businesses

You don’t need to become a WCAG expert overnight. Here is a prioritized action list that addresses the most common issues found during audits — the issues that agencies like Lueur Externe encounter most frequently when auditing client websites.

Quick Wins (Week 1-2)

  • Add alt attributes to every <img> tag. Use descriptive text for informative images; use alt="" for decorative ones.
  • Set the lang attribute on your <html> tag.
  • Ensure every page has a unique, descriptive <title>.
  • Check color contrast with a free tool like WebAIM Contrast Checker.
  • Replace all “Click here” and “Read more” links with descriptive link text.

Structural Fixes (Week 3-4)

  • Verify heading hierarchy: one <h1> per page, then <h2>, <h3>, etc., in logical order — no skipped levels.
  • Add <label> elements to every form input. Use aria-describedby for additional instructions.
  • Ensure your site is fully keyboard-navigable: tab through every page and verify you can reach all interactive elements.
  • Add skip-to-content links.
  • Mark up navigation landmarks (<nav>, <main>, <header>, <footer>).

Advanced Improvements (Month 2-3)

  • Add captions to all video content. Add transcripts to audio content.
  • Audit all JavaScript components (modals, dropdowns, carousels, accordions) for keyboard operability and ARIA compliance.
  • Test with a real screen reader (NVDA is free on Windows; VoiceOver is built into macOS).
  • Publish an accessibility statement (legally required) including: compliance level, non-accessible content list, contact mechanism, and enforcement procedure link.

Code Example: A Properly Accessible Form

Forms are one of the most common failure points. Here is a before-and-after example:

❌ Inaccessible Form

<form>
  <input type="text" placeholder="Your name">
  <input type="email" placeholder="Your email">
  <textarea placeholder="Your message"></textarea>
  <button>Send</button>
</form>

This form has no labels, no fieldset, no error handling, and relies entirely on placeholder text that disappears when the user starts typing — making it unusable for screen reader users and problematic for people with cognitive disabilities.

✅ Accessible Form (RGAA-Compliant)

<form aria-labelledby="contact-heading" novalidate>
  <h2 id="contact-heading">Contact Us</h2>

  <div>
    <label for="name">Full Name <span aria-hidden="true">*</span></label>
    <input type="text" id="name" name="name" required
           aria-required="true"
           aria-describedby="name-hint">
    <span id="name-hint" class="hint">As it appears on your ID.</span>
  </div>

  <div>
    <label for="email">Email Address <span aria-hidden="true">*</span></label>
    <input type="email" id="email" name="email" required
           aria-required="true"
           aria-describedby="email-error" aria-invalid="false">
    <span id="email-error" class="error" role="alert"></span>
  </div>

  <div>
    <label for="message">Your Message</label>
    <textarea id="message" name="message" rows="5"></textarea>
  </div>

  <button type="submit">Send Message</button>
</form>

Notice the differences: explicit <label> elements linked via for/id, aria-required and aria-describedby for additional context, a role="alert" container for dynamic error messages, and a heading to give the form a clear purpose. This is what RGAA criteria 11.1 through 11.13 are looking for.

How Much Does RGAA Compliance Cost?

This is the question every small business owner asks. The honest answer: it depends on your starting point.

ScenarioEstimated Cost RangeTimeline
New website built accessible from scratch+10-15% of base development costIntegrated into project
Existing WordPress/Prestashop site with minor issues€1,500 – €5,0002-6 weeks
Existing site with significant accessibility debt€5,000 – €20,000+2-4 months
Full RGAA audit (106 criteria, sample of pages)€3,000 – €8,0002-4 weeks

The key insight is that building accessible from the start is dramatically cheaper than retrofitting. If you are planning a site redesign or migration, this is the ideal moment to integrate RGAA compliance into the project scope.

Lueur Externe, an agency founded in 2003 and based in the Alpes-Maritimes, has been integrating accessibility best practices into its WordPress and Prestashop builds for years. Their approach — baking compliance into the development workflow rather than treating it as a last-minute audit — consistently reduces both cost and timeline for their clients.

French law requires every website subject to accessibility obligations to publish an accessibility statement (déclaration d’accessibilité). This is not optional — its absence is itself a compliance violation.

Your statement must include:

  • Compliance status: fully compliant, partially compliant, or non-compliant
  • Non-accessible content: a detailed list of what fails and why (technical, exemption, or third-party content)
  • Date of the audit and methodology used
  • Contact mechanism: a way for users to report accessibility issues
  • Enforcement link: a link to the Défenseur des droits for users who do not receive a satisfactory response

This statement must be linked from every page of your website (typically in the footer) and updated at least every three years or after any major redesign.

Common Myths That Get Small Businesses in Trouble

Myth 1: “An accessibility plugin/overlay will make us compliant.”

Reality: Overlay tools (like AccessiBe, UserWay, etc.) add a widget layer on top of your site. They do not fix the underlying code. Multiple studies — including a landmark analysis by the accessibility organization OverlayFactSheet.com signed by over 700 accessibility professionals — have concluded that overlays do not achieve WCAG conformance. Some have actually been the subject of lawsuits themselves. RGAA auditors test the source code, not the overlay.

Myth 2: “We only sell in France, the EU directive doesn’t affect us.”

Reality: The EAA has been transposed into French national law. If you operate in France and provide covered services, you are subject to French enforcement. Selling only domestically provides zero protection.

Myth 3: “Our site uses a CMS template, so it’s the template vendor’s responsibility.”

Reality: You are responsible for the accessibility of your website regardless of what tools you use to build it. Template vendors may provide a more or less accessible starting point, but the content you add, the customizations you make, and the overall user experience are your responsibility.

Tools to Get Started Today

You don’t need to hire an auditor before you lift a finger. These free tools will help you identify your most critical issues:

  • WAVE (wave.webaim.org) — browser extension that visually highlights accessibility errors on any page
  • axe DevTools (by Deque) — a browser extension that runs automated WCAG checks and provides fix suggestions
  • Lighthouse (built into Chrome DevTools) — includes an accessibility score and actionable recommendations
  • Colour Contrast Analyser (by TPGi) — desktop app for precise contrast measurement
  • NVDA (nvaccess.org) — free, open-source screen reader for Windows
  • Tanaguru / Ara — French tools specifically designed for RGAA auditing

Important caveat: Automated tools catch only about 30-40% of RGAA criteria. A full compliance assessment always requires manual testing by a trained auditor. Automated scans are a starting point, not a finish line.

Timeline: What You Should Be Doing Right Now

If you’re reading this in 2025, the deadline is either imminent or already passed. Here is a realistic action plan:

  1. Now: Run automated scans (WAVE, axe) on your top 10 most-visited pages. Document the results.
  2. Week 1-2: Fix all quick wins — alt text, labels, contrast, link text, lang attribute.
  3. Week 3-4: Address structural issues — heading hierarchy, keyboard navigation, landmarks.
  4. Month 2: Commission a professional RGAA audit on a representative sample of pages.
  5. Month 2-3: Fix issues identified in the audit. Prioritize by impact (blocking issues first).
  6. Month 3: Publish your accessibility statement. Set up a user feedback mechanism.
  7. Ongoing: Train your content team. Accessibility is not a one-time project — every new page, blog post, or product listing must maintain compliance.

The 2025 accessibility mandate is real, the penalties are meaningful, and the deadline leaves no room for procrastination. But here’s the reframe that matters: businesses that embrace accessibility early don’t just avoid fines — they gain customers, improve SEO rankings, and future-proof their digital presence.

Accessible websites load faster, convert better, and rank higher. They reach 18% more of the French population. They demonstrate social responsibility in a market where consumers increasingly vote with their wallets.

The gap between where your website is today and where RGAA 4.1 needs it to be might feel daunting. It doesn’t have to be. With the right partner, compliance becomes a structured, manageable project — not a crisis.

Lueur Externe, certified Prestashop expert and WordPress specialist with over 20 years of experience building and optimizing websites from their base in the Alpes-Maritimes, offers comprehensive RGAA compliance services — from initial audits to full remediation and ongoing monitoring. Whether you run a 10-page corporate site or a 10,000-product e-commerce store, their team can build a compliance roadmap tailored to your budget and timeline.

👉 Get in touch with Lueur Externe today to schedule your free accessibility pre-audit and take the first step toward a compliant, inclusive, and higher-performing website.