aiWCAG · WCAG diagnosis and fixes for your website
AIFor the small business with an online store or service website that is already covered by the European Accessibility Act and doesn't know where to start: you enter your website address, choose your key pages, and receive the barriers that need fixing, ordered by what they cost you in sales and with the fix explained.
Responses are generated by artificial intelligence. This is not professional advice and does not replace a qualified professional. In an emergency, contact your local emergency services.

Vous savez déjà que la loi sur l'accessibilité s'applique à vous, mais les rapports qu'on vous envoie sont illisibles et les widgets « magiques » ne corrigent rien ?
aiWCAG ouvre votre site dans un vrai navigateur Chromium, sur mobile et sur ordinateur, et l'analyse avec axe-core selon les critères WCAG 2.0, 2.1 et 2.2 de niveau A et AA, qui constituent la base technique de la norme européenne EN 301 549 et de la European Accessibility Act. Ce que vous recevez n'est pas le déversement du moteur : les erreurs répétées sont regroupées par composant, classées par gravité × portée × emplacement — une icône sans nom sur le bouton « Ajouter au panier » pèse plus que la même erreur dans le pied de page — et chaque carte vous indique la raison de son poids. Chaque constat comporte son critère WCAG, son sélecteur, son HTML et une capture avec l'élément entouré en rouge. Et ce qu'aiWCAG ne fait pas, il le dit à voix haute : il ne certifie pas, n'émet pas de déclarations de conformité et n'installe aucun overlay. Un moteur automatique détecte environ 35 % des barrières réelles ; les corriger est l'étape 1, pas la fin du chemin.
Start for freeDiscover every feature in detail

aiWCAG: which accessibility errors to fix first on your website
aiWCAG ranks your website's WCAG barriers by business impact: severity × reach × element location. Shopping cart issues first, with their reason why.
View feature
aiWCAG: what your accessibility error means and how to fix it
Click a button and aiWCAG's AI explains each WCAG finding: who it excludes, which criterion it violates and how to fix it, with tabs for you and your developer and before/after code.
View feature
Web Accessibility Effort Report: Demonstrate What You’ve Done
aiWCAG generates a chronological document with your audits, each fix with its date and reason, and what’s pending. Read-only link or PDF. It does not certify, and states so.
View feature
aiWCAG: Does the European Accessibility Act apply to me? What the accessibility law requires
Mandatory from June 28, 2025: the European Accessibility Act requires WCAG 2.1 AA via EN 301 549. aiWCAG tells you if it applies to you, what is required, and what no tool can detect.
View featureNot an 80-page PDF: a to-do list
Trois choses qui vont rarement ensemble : un moteur sérieux, un ordre qui comprend votre activité et un rapport que votre développeur peut utiliser tel quel.

A real browser, on mobile and desktop, with the failure highlighted
Up to 5 pages per audit — homepage, listing, product page, cart, and contact; the app suggests them by reading your homepage. Each one is opened twice, on mobile 390×844 and desktop 1366×768, because the hamburger menu or tiny tap targets only fail on mobile. It waits for the network to be idle and scrolls to trigger lazy-load before analyzing, and for every visible finding it saves a screenshot with the element outlined in red. If what the browser sees is not your website — cookie wall, anti-bot block, 403, timeout, or redirect to login — the app tells you with the screenshot of what it saw and a button to retry just that page, instead of returning an empty report that looks good.

Prioritized by business impact and explained by Elena Rius
The 40 images without alt text in the same listing are ONE task that says '×40 across 2 pages,' not 40 cards. The order is not the engine's either: priority = severity × scope × criticality of the place where the element lives, and each card shows why it has that weight ('it's in the cart form'). If you want the why, you click and Elena Rius writes the guide for the finding: who it leaves out in human language, which WCAG criterion it violates and at what level, and how to fix it, with a note for you and another for your developer with the code snippet. AI is only used when you ask for it: nothing is generated behind your back.

Living list, re-audit, and proof of what you've done
Each finding has a status: open, fixed, or dismissed with a reason (false positive, third-party element, not applicable, I accept it). When you re-audit, the app matches findings by a stable hash, automatically closes those that no longer appear, flags new ones, and preserves your dismissals, with a bar chart per audit to see progress. From that come two things worth gold the day someone asks: the effort report, with the timeline of audits and of each status change with its date and reason, and a secure read-only link, expiring and revocable, to send the entire report — screenshots, selectors, and guides — to whoever manages your website without giving them access to your account.
From your website address to the report, in three steps
Enregistrez votre site
Nom, adresse et type d'activité : boutique en ligne, site de services ou autre. Vous pouvez avoir plusieurs sites, un pour chaque site que vous gérez.
Choisissez vos pages clés
La page d'accueil est fixe et vous en ajoutez jusqu'à quatre autres avec leur rôle : listing, fiche produit, panier et contact. Si vous ne les avez pas sous la main, « Suggérer des pages depuis la page d'accueil » les cherche pour vous.
Travaillez le rapport
Vous voyez l'analyse avancer page par page et vous atterrissez sur la liste priorisée. Vous marquez ce qui est corrigé, écartez ce qui ne s'applique pas et relancez un audit quand le code a été modifié.
Frequently asked questions
Latest blog articles
Guides and news to get more out of it

EN 301 549 v4.1.1: what changes in the European accessibility standard and what you need to review on your website
EN 301 549 v4.1.1 (Sept. 2026) moves to WCAG 2.2, removes criterion 4.1.1, and adds 6 requirements. What to review in your online store and why to audit 2.1 and 2.2.

How to know if your website is accessible: the 6 mistakes that cause 96% of WCAG failures
95.9% of websites fail web accessibility and 6 mistakes cause 96% of failures (WebAIM 2026). How to detect them on your website and what the EAA requires in Spain.
Find out today what barriers your website has
Créez votre compte gratuitement, enregistrez votre site et lancez votre premier audit en quelques minutes. aiWCAG est l'outil d'accessibilité web d'AIsToHire.











