Operating ProcedureExecution layer

WCAG Repair Monthly Rescan and Remediation Handoff (Retention)

A sequence with 8 steps: Open the WCAG Repair dashboard and confirm the client site is still registered under the correct workspace before the monthly rescan window opens.

By InnovaAI ResearchPublished

What are the steps?

sequence

WCAG Repair Monthly Rescan and Remediation Handoff (Retention)

  1. 01

    Open the WCAG Repair dashboard and confirm the client site is still registered under the correct workspace before the monthly rescan window opens.

    A site added under the wrong workspace produces an audit certificate that names the wrong domain, which breaks the ADA audit trail the client keeps on file.

  2. 02

    Launch the monthly rescan on the client URL and let axe-core run against WCAG 2.1 and 2.2 AA success criteria.

    Free scans cap at 10 pages; paid plans reach 100 pages. If the client added templates or landing pages since last month, raise the page count before the scan starts so new URLs are not silently skipped.

  3. 03

    Compare the new violation list against last month's baseline and separate regressions from carry-over issues.

    A regression is any issue that was clean last cycle and reappeared. Regressions usually trace to a theme update, a new CMS block, or a plugin release, and they belong at the top of the client conversation.

  4. 04

    Generate the AI remediation guide and pull the copy-paste code fixes for every open issue.

    The guide ranks fixes by impact and includes platform-specific instructions for WordPress, Shopify, and React, plus effort estimates per fix. Hand the guide to whoever owns the client's codebase rather than paraphrasing it.

  5. 05

    Assign each fix to the delivery owner and set a due date inside the current retainer cycle.

    Keep the priority ranking intact. Reordering fixes by developer preference is how low-effort contrast and alt-text items get deferred behind structural ARIA work that takes longer to ship.

  6. 06

    Re-run the scan on the affected pages after fixes deploy and confirm the violations clear.

    Spot-check the specific URLs that were flagged instead of trusting a full-site pass, because a single cleared page can mask a template that still emits the same error on sibling pages.

  7. 07

    Download the updated audit certificate and refresh the embeddable badge on the client site.

    The certificate and badge are the client-facing proof for ADA, Section 508, and EAA documentation. Replace the prior month's assets so the client is not displaying a stale compliance date.

  8. 08

    Log the remediation entries in the client's compliance dashboard and send the branded monthly progress report.

    The report should show issues closed, issues opened, and the current open count. That running log is what the client hands to a regulator or a procurement reviewer, so it needs to match the certificate exactly.