Audit Timeline

title: "Audit Timeline and Planning" weight: 24 description: "Learn how to plan and schedule accessibility audits: define phases with time estimates, allocate resources, manage dependencies, handle scope changes, and coordinate across teams for timely delivery." date: 2026-06-28 lastmod: 2026-06-28 tags: [accessibility, auditing]

Audit timeline and planning involves breaking the audit into phases (scope, scan, manual review, reporting, remediation, re-audit), estimating time for each phase, allocating resources, managing dependencies, and creating a schedule that aligns with development cycles.

## What You'll Learn

You will estimate audit duration, create timelines, allocate resources, manage dependencies, and handle common scheduling challenges.

## Why It Matters

Poor planning leads to delayed reports, rushed evaluations, and missed compliance deadlines. A well-planned audit schedule ensures thorough evaluation, timely delivery, and actionable results within the business timeline.

## Real-World Use

A company needs WCAG AA compliance documentation before a Q4 sales cycle. The audit starts in August: scope (1 week), automated scanning (1 week), manual review (3 weeks), reporting (1 week). Remediation runs September-October. Re-audit in early November confirms compliance.

## Audit Timeline

```mermaid
flowchart TD
  A[Week 1: Scope Definition] --> B[Week 2: Automated Scan]
  B --> C[Weeks 3-5: Manual Review]
  C --> D[Week 6: Reporting]
  D --> E[Weeks 7-10: Remediation]
  E --> F[Week 11: Re-audit]
  F --> G[Week 12: Final Report]

Planning an Audit

Estimate time based on page count, complexity, and team size.

<!-- Timeline estimation template -->
<div class="estimation">
  <h3>Audit Effort Estimation</h3>
  <table>
    <tr><th>Phase</th><th>Per Page</th><th>50 Pages</th></tr>
    <tr><td>Automated scan</td><td>2 min</td><td>2 hours</td></tr>
    <tr><td>Manual keyboard test</td><td>15 min</td><td>12.5 hours</td></tr>
    <tr><td>Screen reader test</td><td>20 min</td><td>17 hours</td></tr>
    <tr><td>Visual inspection</td><td>10 min</td><td>8 hours</td></tr>
    <tr><td>Documentation</td><td>10 min</td><td>8 hours</td></tr>
    <tr><td><strong>Total</strong></td><td><strong>57 min</strong></td><td><strong>47.5 hours</strong></td></tr>
  </table>
</div>

/* Timeline visualization */
.timeline {
  display: flex;
  gap: 4px;
  padding: 1rem;
}

.phase {
  padding: 0.5rem;
  border-radius: 4px;
  text-align: center;
  font-size: 0.8rem;
}

.phase-scope { background: #e3f2fd; width: 8%; }
.phase-scan { background: #bbdefb; width: 8%; }
.phase-manual { background: #90caf9; width: 25%; }
.phase-report { background: #64b5f6; width: 8%; }
.phase-remediation { background: #42a5f5; width: 34%; }
.phase-reaudit { background: #2196f3; width: 17%; }

// Timeline calculator
function calculateAuditTimeline(pages, teamSize) {
  const hoursPerPage = {
    automated: 0.03,
    keyboard: 0.25,
    screenReader: 0.33,
    visual: 0.17,
    documentation: 0.17
  };

  const totalHours = Object.values(hoursPerPage)
    .reduce((sum, h) => sum + h * pages, 0);

  const weeks = Math.ceil(totalHours / (teamSize * 35)); // 35hr weeks

  return {
    totalHours: Math.round(totalHours),
    teamSize,
    estimatedWeeks: weeks,
    phases: [
      { name: 'Scope', weeks: 1 },
      { name: 'Automated Scan', weeks: 0.5 },
      { name: 'Manual Review', weeks: weeks * 0.4 },
      { name: 'Reporting', weeks: 1 },
      { name: 'Remediation', weeks: weeks * 0.6 },
      { name: 'Re-audit', weeks: weeks * 0.3 }
    ]
  };
}

console.log(calculateAuditTimeline(50, 2));

Common Mistakes

• Underestimating manual review time
• Not accounting for reporting and documentation
• Scheduling audits during code freezes or holiday periods
• Not building buffer time for unexpected findings
• Planning remediation without estimating effort
• Ignoring dependencies on other teams
• Not aligning audit cadence with release cycles

Practice and Challenge

Practice 1: Estimate the timeline for auditing a 20-page marketing site. Practice 2: Create a timeline for a 200-page enterprise portal. Practice 3: Identify dependencies between audit phases. Practice 4: Build buffer time into an audit schedule. Practice 5: Create a milestone checklist for audit delivery.

Challenge: A company with 100 critical pages needs an audit before a regulatory deadline in 12 weeks. Create a detailed week-by-week timeline including scope, automated scan, manual review (with 2 auditors), reporting, remediation planning, and re-audit. Include milestones, dependencies, buffer time, and a risk management section.

FAQ

Mini Project

Create a complete audit project plan for a SaaS platform with 75 pages. Include: Gantt chart with phases, effort estimation table, resource allocation (2 auditors, 1 remediation lead, 4 developers), dependency map, milestone checklist, risk register, and a communication plan for weekly stakeholder updates.

What's Next

Auditing Module Project covers the capstone project for the auditing module.