Agentic Fixes is AllAccessible's human-in-the-loop agentic AI remediation. AllAccessible AI (✦) reviews your recent audits, drafts specific fixes for common accessibility issues, and groups them so one fix can apply across every page it appears on. Nothing goes live until you approve it. This guide walks through reviewing proposed fixes, approving and deploying them, and reverting a fix if you change your mind.

The model is: your AI auto-suggests, your team approves. Fixes are drafted for you, but you stay in control — review each one, edit it if needed, and approve only what you want. Approved fixes are applied by the widget at runtime as accessibility attributes; they don't change your site's visual design or page structure.

AllAccessible AI reviews your recent audits and drafts targeted fixes — things like adding an accessible label to an unlabeled button, adding text to an empty link, or setting the page language. Because the same issue often repeats across many pages, fixes are grouped: one card can represent a fix that applies everywhere that issue appears.

Fixes are applied by the widget at runtime as accessibility attributes (for example, an aria-label). Approving a fix does not alter your site's visual layout or DOM structure — it layers accessibility information on top on the next page load.

Image alt text is handled separately in the Image Manager, not here.

Beta: Agentic Fixes carries a Beta badge. The core review-and-approve flow is stable; you may see labels and copy continue to evolve.

The page is titled Agentic Fixes with a Beta badge. Its description reads: "Each card below is a fix that appears on multiple pages. Review, edit if needed, then approve to apply everywhere at once." A summary line tells you how much is waiting, e.g. "12 unique fixes ready to review across 40 pages."

📷 Agentic Fixes grouped view with fix cards

Fixes are organized into status tabs:

Start in Pending review.

Each card is written in plain English so you can make a decision without reading code. A card shows:

If you want the technical specifics, expand Developer details to see the targeted element and issue type.

📷 A single Agentic Fix card with its title, proposed change, and page count

Every card tells you where the fix will land — this directly answers "which pages does this touch?":

Use these before approving so you know the full scope of what you're applying.

While a fix is still a draft, you can adjust it. Click the Edit (pencil) control, change the value (for example, reword an aria-label), and choose Save changes. Once a fix is approved, its value is locked, so make edits before approving.

There are two approval surfaces depending on where you are:

Once approved, the card moves to Approved & applied and shows an Applied state. The widget picks up approved fixes and renders them on the next page load — there's nothing else to install.

📷 The Approve on N pages button on a fix card

Changed your mind, or a fix didn't land the way you expected? You can undo it.

The fix stops being applied and moves to the Reverted tab, where it stays as an archived record. Reverting is safe — because fixes only add accessibility attributes at runtime, removing one simply returns the page to its prior state.

If your Pending review tab is empty, you can prompt AllAccessible AI to draft fixes on demand. The empty state offers a Generate fixes now button, which reviews your last 30 days of audits and drafts fix cards from them. While it works, you'll see a "Generating fixes…" state — "Your AI is reviewing recent audits and drafting fixes." When it finishes, refresh the Pending review tab to see the new cards.

Q: Will approving a fix change how my site looks?
A: No. Approved fixes add accessibility attributes (like aria-label) that the widget applies at runtime. There are no visual or page-structure changes.

Q: Do I have to approve everything at once?
A: No. Review and approve fixes one card at a time. Approve the ones you're confident in and leave the rest in Pending review.

Q: What does the confidence percentage mean?
A: It's how confident AllAccessible AI is in that specific proposed fix. Higher-confidence fixes are usually safe, obvious corrections; lower-confidence ones are worth a closer look and possibly an edit before approving.

Q: Can I change the wording of a fix?
A: Yes — while it's still a draft. Use the Edit pencil, adjust the value, and Save changes. After approval the value is locked; revert first if you need to change an applied fix.

Q: What about image alt text?
A: Alt text is managed in the Image Manager, not in Agentic Fixes. Agentic Fixes links there for image-related work.

Q: Is this the same as guaranteeing my site is compliant?
A: No. Agentic Fixes helps you remediate common issues efficiently as part of an ongoing, good-faith accessibility effort. It doesn't certify compliance or replace manual testing.

Cause: Agentic Fixes can be viewed on legacy widget (v1) sites, but fixes can only be deployed on the current widget (v2). On a v1 site the approve button is disabled, with a note that Agentic Fixes are read-only and a prompt to upgrade to widget v2.

Solution: Upgrade the site to the current widget version to enable deploying fixes. Until then, you can review proposed fixes but not apply them.

Possible causes:

Solutions:

Cause: Access is available to the site owner and team members with access to that site. An unexpected error usually indicates an access or membership problem.

Solution: If you should have access and hit an error, contact support rather than assuming it's expected.

Last Updated: July 2026
​Where: Audits & Fixes → Agentic Fixes (Beta)
​Note: Human-in-the-loop agentic AI remediation — your AI drafts, you approve. Deploying fixes requires the current widget (v2).