# aiWCAG | Web accessibility audit WCAG and EAA

> Analyze up to 5 pages of your website with axe-core on mobile and desktop: WCAG barriers prioritized by business, with screenshots and fixes. It does not certify, and says so.

- **Source (source):** https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176
- **Platform (platform):** AIstoHire
- **Language (language):** en
- **Updated (updated):** 2026-11-20

## In summary

- WCAG diagnosis and fixes for your website
- For 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.
- 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.

## Do you already know the accessibility law applies to you, but the reports you're sent are unreadable and the 'magic' widgets fix nothing?

aiWCAG opens your website in a real Chromium browser, on mobile and desktop, and analyzes it with axe-core against WCAG 2.0, 2.1, and 2.2 Level A and AA criteria, which are the technical basis of the European standard EN 301 549 and the European Accessibility Act. What you receive is not the engine's raw output: repeated errors are grouped by component, ordered by severity × scope × where they are — an unnamed icon on the 'Add to cart' button weighs more than the same failure in the footer — and each card tells you why it has that weight. Every finding includes its WCAG criterion, its selector, its HTML, and a screenshot with the element outlined in red. And what aiWCAG doesn't do, it says out loud: it doesn't certify, doesn't issue conformance statements, and doesn't install any overlay. An automated engine detects around 35% of real barriers; fixing them is step 1, not the end of the road.

## Not an 80-page PDF: a to-do list

Three things that don't usually go together: a serious engine, an order that understands your business, and a report your developer can use as is.

### 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

1. **Register your website** — Name, address, and business type: online store, service website, or other. You can have multiple sites, one for each website you manage.
2. **Choose your key pages** — The homepage is fixed, and you add up to four more with their role: listing, product page, cart, and contact. If you don't have them at hand, 'Suggest pages from homepage' finds them for you.
3. **Work through the report** — You watch the analysis progress page by page and land on the prioritized list. You mark what's fixed, dismiss what doesn't apply, and re-audit when the code has been changed.

## Frequently asked questions

### Does aiWCAG certify that my website complies with the EAA?

No, and that's a design decision, not an oversight. aiWCAG does not issue badges, certificates, or accessibility conformance statements, and on no screen will it tell you that your website 'is already accessible': an automated engine detects around 35% of real barriers, and the rest — whether someone can actually navigate with a keyboard, whether a photo's alt text says something useful, whether videos have captions, whether the content is understandable — requires a manual review that no tool can do on its own. What aiWCAG gives you is the automatable part, complete and prioritized, with the coverage notice always visible: in the report, in the printable view, and in any link you share. It is not legal advice either.

### What exactly does it detect, and what does it miss?

It detects what an engine can check on already-rendered code: insufficient contrast, images without alt text, buttons and links without accessible names, form fields without labels, out-of-order headings, misused ARIA attributes, missing page language, poorly constructed lists and tables, or elements that cannot be focused. It runs with axe-core, the same engine behind the industry's reference extensions, with WCAG 2.0, 2.1, and 2.2 Level A and AA rules enabled and 'best practices' rules disabled, so only normative issues appear. It misses everything that requires human judgment: logical reading order, whether alt text is correct or merely present, captions and audio description, plain language, PDFs on your website, and any area that requires a password. The app lists this point by point in its EAA section.

### What if my website has a cookie wall or is behind Cloudflare?

This is the most common case, and the app treats it as what it is: an issue, not a clean report. If a consent banner covers more than 40% of the screen or a known manager is detected (OneTrust, Cookiebot, Didomi, and similar), the page is still analyzed but is marked as 'analyzed with a cookie wall present,' and the report warns that results may be incomplete. If what responds is an anti-bot challenge, a 403, or a timeout, that page appears with the exact reason, a screenshot of what the browser saw, advice on how to unblock it, and a button to retry just that page. The other pages in the report remain valid while you resolve that one.

### Can I share the report with whoever manages my website?

Yes, and it's designed for exactly that. From the report, you create a secure read-only link, expiring in 7, 30, or 90 days and revocable whenever you want, that opens the full report in the browser of whoever receives it, without an account and without access to anything else of yours: screenshots with the element highlighted, WCAG criterion, copyable CSS selector and HTML, and any guides you've generated. You choose what it includes — warnings, dismissed items, technical detail — and the view includes print styles, so it can be saved as a PDF from the browser itself. There is a second link for the effort report, with the timeline of audits and measures taken.

## Features in detail

- [aiWCAG: which accessibility errors to fix first on your website](https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176/f/prioritize-accessibility-errors-by-business-impact) — aiWCAG ranks your website's WCAG barriers by business impact: severity × reach × element location. Shopping cart issues first, with their reason why.
- [aiWCAG: what your accessibility error means and how to fix it](https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176/f/ai-explanation-of-each-accessibility-error) — 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.
- [Web Accessibility Effort Report: Demonstrate What You’ve Done](https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176/f/printable-accessibility-effort-report) — 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.
- [aiWCAG: Does the European Accessibility Act apply to me? What the accessibility law requires](https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176/f/what-the-eaa-requires-european-accessibility-act) — 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.

- [Blog](https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176/blog)

## About the platform

**aiWCAG — Web accessibility audit (WCAG and EAA)** — an app by AIstoHire. Available at: https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176

### Other languages

- `es`: https://aistohire.com/es/aiwcag-auditoria-accesibilidad-web-wcag-eaa-176
- `fr`: https://aistohire.com/fr/aiwcag-audit-accessibilite-web-wcag-eaa-176
- `it`: https://aistohire.com/it/aiwcag-audit-accessibilita-web-wcag-eaa-176
- `pt`: https://aistohire.com/pt/aiwcag-auditoria-acessibilidade-web-wcag-eaa-176
- `de`: https://aistohire.com/de/aiwcag-web-barrierefreiheits-audit-wcag-eaa-176
- `bg`: https://aistohire.com/bg/aiwcag-odit-na-ueb-dostapnostta-wcag-i-eaa-176
- `ja`: https://aistohire.com/ja/web-accessibility-audit-wcag-eaa-176
- `nl`: https://aistohire.com/nl/aiwcag-audit-van-webtoegankelijkheid-wcag-en-eaa-176
- `ko`: https://aistohire.com/ko/web-accessibility-audit-wcag-eaa-176
- `sv`: https://aistohire.com/sv/aiwcag-granskning-av-webbtillganglighet-wcag-och-eaa-176
- `da`: https://aistohire.com/da/aiwcag-audit-af-webtilgaengelighed-wcag-og-eaa-176
- `ar`: https://aistohire.com/ar/aiwcag-tdqiq-imkania-wsul-almuaqa-wcag-weaa-176
- `no`: https://aistohire.com/no/aiwcag-revisjon-av-universell-utforming-wcag-og-eaa-176
- `fi`: https://aistohire.com/fi/aiwcag-wcag-ja-eaa-saavutettavuusauditointi-verkkosivustolle-176
- `zh`: https://aistohire.com/zh/aiwcag-web-accessibility-audit-176
- `pl`: https://aistohire.com/pl/aiwcag-audyt-dostepnosci-strony-wcag-i-eaa-176
- `he`: https://aistohire.com/he/aiwcag-bikort-ngishot-atrim-wcag-v-eaa-176
- `cs`: https://aistohire.com/cs/aiwcag-audit-pristupnosti-webu-wcag-a-eaa-176
- `id`: https://aistohire.com/id/aiwcag-audit-aksesibilitas-web-wcag-dan-eaa-176
