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

- **Source (source):** https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176/f/prioritize-accessibility-errors-by-business-impact
- **Platform (platform):** AIstoHire
- **Language (language):** en

## In summary

- What to fix first: your accessibility barriers sorted by business impact
- aiWCAG doesn't just dump the engine output in alphabetical order: it puts the issue in your add-to-cart button at the top and tells you why it's there.
- The shopping cart issue, at the very top
- Each card explains its position
- Three levels, no score

## What to fix first: your accessibility barriers sorted by business impact

When aiWCAG finishes analyzing your pages, each finding receives a priority number calculated from three factors that multiply together. The first is the technical severity given by axe-core: critical, serious, moderate, or minor, with weights from 4 to 1. The second is the scope: how many times the same issue appears and whether it repeats across more than one page; it grows logarithmically, because going from 2 to 40 images without alternative text matters, but not twenty times more. The third is what almost no report looks at: where the element lives.

That element criticality is derived from two things. From its actual position in the HTML—aiWCAG checks whether the element is inside a button, a form, the navigation, the main content, or the footer—and from the role you gave the page when configuring the audit. A button or form weighs 3; main navigation, 3; content, 2; footer, 1. And if that button or form is on a page you marked as shopping cart, the weight rises to 4.5. The same icon without an accessible name weighs almost five times more in your checkout than in the footer, because that's where it costs you money.

From the number comes a visible level, and only three: Critical, Severe, and Warning. No scores from 0 to 100 or passing grades that someone later shows off as if it were a certificate. A critical issue is always critical; a serious one escalates to critical if it's in a critical area, and stays severe if it's in a quiet zone. And on each card, below the title, the reason for its weight is written in words: "It's in a button or form in the shopping area," "It's in the main navigation," "It's in the footer." If the order doesn't make sense to you, you can argue it, because you know where it comes from.

The default order of the task list is that one, business impact, but you're not tied to it: you can reorder by pure technical severity if your developer prefers to tackle by issue type, or by page if you're going to work on a specific template. You can also filter the list by tapping a level, and when you request Elena Rius's explanations in batch, the "critical and severe only" button uses this same classification to avoid spending on warnings.

## What's included

- **The shopping cart issue, at the very top** — criticality multiplies by 4.5 what's in a button or form in the shopping area, and by 1 what's in the footer. The result is a list that starts where you lose customers, not where the engine found the first error.
- **Each card explains its position** — below the title is the reason for its weight in a readable sentence («It's in a form», «It's in the main navigation»). It's not a black box that spits out a number: you see why that finding is where it is and you can question it.
- **Three levels, no score** — Blocker, Severe, and Warning. aiWCAG doesn't give you a 78 out of 100 that someone could show off as if it were a compliance badge, because that score doesn't exist in the standard and would give a false sense of compliance.
- **40 occurrences are one task, not 40** — findings are grouped by rule and component, and scope factors into priority with a «×40 on 2 pages» on the card. You work from a human-sized task list, not a 300-line dump.
- **Reorder when it suits you** — the default order is business impact, but you switch to technical severity or page with two taps, and filter by level by tapping a counter. Your compliance officer and your developer can each read the same audit their own way.
- **The site's weighted severity moves with your work** — the sum of priorities of what remains open is shown as a bar in five ranges, from Minimal to Very high. If you fix two blockers in checkout, it drops much more than if you check off ten warnings in the footer.

## Frequently Asked Questions

### How does aiWCAG decide which accessibility error is most urgent?

With a priority that multiplies three factors: the technical severity given by axe-core (critical 4, serious 3, moderate 2, minor 1), the scope (number of occurrences on a logarithmic scale, plus extra if the finding appears on multiple pages), and the criticality of the element, which is 4.5 if it's in a button or form on a page marked as a shopping cart, 3 in buttons, forms and navigation, 2 in the main content and 1 in the footer. That number determines the default order of the task list.

### Does the prioritization measure my actual sales or my analytics?

No, and it's important to know this. aiWCAG does not connect to your analytics or your payment gateway: the "business impact" is inferred from the element's position in the HTML (whether it's inside a button, a form, the navigation, the content or the footer) and from the role you assigned to each page when configuring the audit (main, listing, product, shopping cart, contact). It's a transparent and reviewable heuristic, not an estimate of lost revenue.

### What do Bloqueante, Severo and Advertencia mean?

They are aiWCAG's three visible levels. A finding with critical impact is always Bloqueante. One with serious impact is Bloqueante if it lives in a critical zone (button, form, navigation or shopping cart) and Severo if it doesn't. A moderate one is Severo in a critical zone and Advertencia elsewhere, and minor ones are always Advertencia. There is no fourth level or an overall score-type rating, by design: no automated tool can certify conformance.

### Can I change the order if my developer prefers a different criterion?

Yes. The list starts sorted by business priority, but you can reorder it by pure technical severity or by page, filter by level by tapping the summary counters, filter by status (open, fixed, dismissed) or by viewport, and search by name or WCAG criterion. The priority calculation doesn't change: what changes is how you read it.

### Does the priority change when I audit again?

Yes, because it's recalculated in each audit with the data from that run. If you fix the add-to-cart button issue, it disappears from the list and the site's weighted severity (the sum of priorities of what remains open, displayed as a bar in five ranges from Minimal to Very high) drops noticeably. If you only check off warnings in the footer, it barely moves: that's exactly what prioritization is meant to show you.

- [aiWCAG — Web accessibility audit (WCAG and EAA)](https://aistohire.com/aiwcag-web-accessibility-audit-wcag-eaa-176)

## 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/f/prioritize-accessibility-errors-by-business-impact

### Other languages

- `es`: https://aistohire.com/es/aiwcag-auditoria-accesibilidad-web-wcag-eaa-176/f/priorizar-errores-accesibilidad-por-impacto-de-negocio
- `fr`: https://aistohire.com/fr/aiwcag-audit-accessibilite-web-wcag-eaa-176/f/prioriser-erreurs-accessibilite-par-impact-business
- `it`: https://aistohire.com/it/aiwcag-audit-accessibilita-web-wcag-eaa-176/f/prioritizzare-errori-accessibilita-per-impatto-business
- `pt`: https://aistohire.com/pt/aiwcag-auditoria-acessibilidade-web-wcag-eaa-176/f/priorizar-erros-acessibilidade-por-impacto-negocio
- `de`: https://aistohire.com/de/aiwcag-web-barrierefreiheits-audit-wcag-eaa-176/f/barrierefreiheitsfehler-nach-geschaeftlicher-auswirkung-priorisieren
- `bg`: https://aistohire.com/bg/aiwcag-odit-na-ueb-dostapnostta-wcag-i-eaa-176/f/prioritizirane-na-greshki-v-dostapnostta-po-biznes-vazdeystvie
- `ja`: https://aistohire.com/ja/web-accessibility-audit-wcag-eaa-176/f/accessibility-error-priority-business-impact
- `nl`: https://aistohire.com/nl/aiwcag-audit-van-webtoegankelijkheid-wcag-en-eaa-176/f/toegankelijkheidsfouten-prioriteren-naar-zakelijke-impact
- `ko`: https://aistohire.com/ko/web-accessibility-audit-wcag-eaa-176/f/jeobgeunseong-oryu-useonsunwi-bijeuniseu-yeonghyang
- `sv`: https://aistohire.com/sv/aiwcag-granskning-av-webbtillganglighet-wcag-och-eaa-176/f/prioritera-tillganglighetsfel-efter-affarspaverkan
- `da`: https://aistohire.com/da/aiwcag-audit-af-webtilgaengelighed-wcag-og-eaa-176/f/prioriter-tilgaengelighedsfejl-efter-forretningspaavirkning
- `ar`: https://aistohire.com/ar/aiwcag-tdqiq-imkania-wsul-almuaqa-wcag-weaa-176/f/tartib-akhta-alitaha-bihasab-alathar-ala-alnashat
- `no`: https://aistohire.com/no/aiwcag-revisjon-av-universell-utforming-wcag-og-eaa-176/f/prioritere-tilgjengelighetsfeil-etter-virkning-pa-virksomheten
- `fi`: https://aistohire.com/fi/aiwcag-wcag-ja-eaa-saavutettavuusauditointi-verkkosivustolle-176/f/saavutettavuusvirheiden-priorisointi-liiketoimintavaikutuksen-mukaan
- `zh`: https://aistohire.com/zh/aiwcag-web-accessibility-audit-176/f/youxian-chuli-wuzhangai-cuowu-shangye-yingxiang
- `pl`: https://aistohire.com/pl/aiwcag-audyt-dostepnosci-strony-wcag-i-eaa-176/f/priorytetyzacja-bledow-dostepnosci-wedlug-wplywu-na-biznes
- `he`: https://aistohire.com/he/aiwcag-bikort-ngishot-atrim-wcag-v-eaa-176/f/prioritize-accessibility-errors-by-business-impact
- `cs`: https://aistohire.com/cs/aiwcag-audit-pristupnosti-webu-wcag-a-eaa-176/f/priorizace-chyb-pristupnosti-podle-dopadu-na-byznys
- `id`: https://aistohire.com/id/aiwcag-audit-aksesibilitas-web-wcag-dan-eaa-176/f/prioritas-kesalahan-aksesibilitas-menurut-dampak-bisnis
