Every finding in your audit has an AI button showing the cost upfront and the promise that nothing is charged until you press it: in return you get who you're leaving out, which WCAG criterion you're failing, and the fix in two versionsāone for you and one for whoever touches the code.
"Elements must have sufficient color contrast." Okay. And who does that bother, what law does it break, and what do I tell my developer?
When you open a finding card in aiWCAG you already have the objective facts: the WCAG criterion, the CSS selector, the element's HTML, and a screenshot with the issue circled in red. What you don't have is the why. For that, at the bottom of the card there's a single buttonā"Generate impact and solution guide with AI Ā· ~1,600 tokens"āwith the estimated cost written inside and, below it, the line that matters: "Nothing is charged until you press." This app's AI doesn't fire on its own, doesn't analyze anything behind your back, and doesn't charge for looking: scanning your site consumes no tokens, and the explanation only exists if you request it, finding by finding.
When you press, Elena Riusāthe digital accessibility and European Accessibility Act specialist who accompanies the entire appāwrites the guide for THAT specific finding, with its selector and HTML in front of her, and returns it in three blocks. "Who it leaves out" translates the error into people: who can't complete a purchase, with what assistive technology, and at what point in their journey. "Why it affects you legally" names the WCAG criterion being violated and its level, and connects it to the European regulation. "How to fix it" opens in two tabs: "For you," in the language of someone who manages a website, and "For your developer," with the technical change and a before/after code snippet that copies with one tap.
Elena has one rule above all others: not to sell you compliance. The system actively filters out phrases like "this makes you EAA compliant" before showing you the text, and each guide comes signed with a footer that can't be removed: "Written by Elena Rius Ā· guidance only, not legal advice." The guide tells you how to fix a finding, not that your site is compliant.
What you spend is transparent and reversible on its terms: the 1,600 tokens are an estimate, the final charge is for the tokens the generation actually consumes, and if the AI call fails nothing is deducted. If you want another version of the same finding, the button below says exactly what will happenā"Regenerate (charged)"āand the already-generated guide stays saved in the finding, so reopening the card tomorrow is free. Plus, when another user has already requested the guide for that same WCAG rule, aiWCAG reuses the common part and the estimate drops to about 900 tokens.
The price is written on the button
the estimated cost in tokens is shown inside the button itself before touching it, with the notice "Nothing is charged until you press" right below. No generation happens by default, neither when opening the card nor when finishing the audit.
Three questions, three separate answers
who it leaves out (people and assistive technologies), why it affects you legally (WCAG criterion, level, and fit within the European regulation), and how to fix it. It's not a generic paragraph about contrast: Elena writes with the selector and HTML of YOUR element in front of her.
"For you" and "For your developer" in two tabs
the same solution explained twice, so you don't have to translate anything or forward text you don't understand. You decide which tab you read and which one you forward to whoever manages your website.
Code, before and after, copyable with one tap
the technical tab includes the snippet with the current state and the corrected version, plus a copy button right next to it. Your developer doesn't have to guess which of the four header buttons it was.
Elena doesn't sign off on compliance
the system removes phrases suggesting achieved conformance before you read them, and each guide includes the footer "informational, not legal advice". aiWCAG doesn't certify, and neither does the explanation of each finding.
Generated content persists, regenerating warns it costs
the guide is saved in the finding and reviewing it again costs nothing. If you request a new version, the button says so in its own label. And if the AI doesn't respond, nothing is charged.
A configurable engine, not a black box
the explanation is generated with the AI engine configured for the app, the same one you see declared in its specs. It's the only point in all of aiWCAG where generative AI is used; the technical analysis is done by axe-core in a real browser, with no language models involved.

Create your free AIsToHire account, register your site and launch your first audit: scanning doesn't consume tokens and you request AI guides one by one, with the cost always visible.