Re Audit

title: "Re-audit Process" weight: 21 description: "Learn how to conduct re-audits after remediation to verify fixes, check for regressions, update compliance status, and close the remediation loop with documented evidence." date: 2026-06-28 lastmod: 2026-06-28 tags: [accessibility, auditing]

A re-audit verifies that remediation efforts have resolved documented issues, checks for regressions introduced by fixes, and updates the compliance assessment -- closing the audit loop with evidence that each finding is addressed.

## What You'll Learn

You will plan and execute re-audits, verify individual fixes, check for regressions, update compliance documentation, and close issues with evidence.

## Why It Matters

Without re-audit, you cannot confirm that fixes actually resolved the issues. Re-audit provides the evidence needed for compliance claims, legal defense, and stakeholder confidence that the accessibility investment delivered results.

## Real-World Use

After a 4-sprint remediation, the auditor re-tests all 50 issues. 48 are confirmed fixed, 1 has a different issue in the same component, and 1 was not actually fixed (the developer misunderstood the requirement). The remaining 2 are documented for a follow-up sprint.

## Re-audit Workflow

```mermaid
flowchart TD
  A[Remediation Complete] --> B[Re-audit Planning]
  B --> C[Verify Fixed Issues]
  C --> D[Check for Regressions]
  D --> E{Run Full Scan?}
  E -->|Yes| F[Full automated scan]
  E -->|No| G[Selective testing]
  F --> H[Update Compliance]
  G --> H
  H --> I[Close or Re-open]

Performing Re-audit

For each documented issue, test that the fix is implemented correctly and no new issues were introduced.

<!-- Before remediation -->
<img src="product.jpg">
<button onclick="submit()">Submit</button>

<!-- After remediation: verify fixes -->
<img src="product.jpg" alt="Wireless headphones in black">
<button onclick="submit()" aria-label="Submit order">Submit</button>

/* Before remediation: contrast failure */
.cta-button { background: #ddd; color: #666; }

/* After remediation: verify contrast passes */
.cta-button { background: #0066cc; color: #fff; }
/* Re-audit confirms 5.1:1 contrast ratio - passes AA */

// Re-audit tracking
const reAuditResults = {
  auditDate: '2026-06-28',
  totalIssues: 50,
  confirmedFixed: 48,
  notFixed: 1,
  regressionNew: 1,
  complianceAchieved: false,
  notes: 'One issue misunderstood by developer. One regression from CSS refactor.'
};

// Verification function
function verifyFix(issue, pageUrl) {
  const result = runAccessibilityCheck(pageUrl, issue.wcag);
  return {
    issueId: issue.id,
    fixed: !result.violations.find(v => v.id === issue.ruleId),
    evidence: result.evidence
  };
}

Common Mistakes

• Re-testing only the issues without checking for regressions
• Running only automated scans for re-audit
• Not updating the compliance assessment after fixes
• Forgetting to test edge cases around fixed components
• Closing issues without screenshot evidence
• Re-auditing only a subset of pages
• Not documenting the re-audit methodology

Practice and Challenge

Practice 1: Create a re-audit checklist for verifying 10 sample fixes. Practice 2: Write a procedure for checking regressions after a fix. Practice 3: Create a re-audit report template with pass/fail per issue. Practice 4: Calculate the fix rate and regression rate for a sample re-audit. Practice 5: Define what evidence is needed to close an issue.

Challenge: Given an initial audit with 30 findings and a completed remediation plan, create a complete re-audit report. Include: re-audit methodology, issue-by-issue verification results, regression check across all pages, updated severity distribution (remaining issues), updated compliance verdict, and recommendations for ongoing monitoring.

FAQ

Mini Project

Create a re-audit verification dashboard that tracks the status of each issue through the remediation lifecycle: open, in-progress, fixed, verified, closed. Include a re-audit checklist template, a verification script that runs axe-core on specific selectors, and a report generator that produces a before/after comparison.

What's Next

Audit CI/CD Integration covers integrating audit checks into development pipelines.