2026-05-17 · 5 min read

How Long Does a WCAG Audit Take? A Government IT Director's Timeline Guide

# How Long Does a WCAG Audit Take? A Government IT Director's Timeline Guide

Government agencies planning for the DOJ Title II April 2027 deadline need to know how much time to budget for a WCAG audit — not just the cost, but the calendar time from engagement to final deliverable. The answer determines whether you have enough runway for a full remediation cycle before the deadline.

This post gives realistic timeframes based on actual government site auditing, organized by scope and methodology — not vendor marketing copy.

The Honest Timeline Breakdown

Automated scan only: 1 to 3 days

An automated scan using axe-core, Lighthouse, or WAVE across a government website of any size can complete in hours. A 500-page site can be scanned overnight. The deliverable — a raw export of detected failures — takes another day to organize and format.

What this gets you: Detection of approximately 57% of WCAG failures. The half you get is real and useful: missing alt text, contrast failures, missing form labels, missing document language declarations. The half you don't get — keyboard navigation failures, screen reader interaction problems, focus management errors, cognitive usability issues — requires manual testing.

An automated scan report is a useful starting point and a dangerous endpoint. As a standalone compliance document, it will not survive DOJ scrutiny.

Calendar time to final report: 1 to 3 business days.

Automated + limited manual (50 representative pages): 2 to 3 weeks

A credible hybrid audit selects a representative page sample — covering major page templates, key service forms, document types, and navigation patterns — and applies both automated tools and manual testing with assistive technology.

For 50 representative pages:

• Automated scan: 1-2 days
• Manual keyboard navigation review: 2-4 days (experienced auditor, 15-30 min per page type, testing at least one example of each template)
• Screen reader testing (NVDA + Chrome, VoiceOver + Safari): 3-5 days
• Findings compilation, severity rating, and report writing: 3-5 days
• Accessibility statement draft: 1 day

Total: 10 to 17 business days (2 to 3.5 weeks).

What this gets you: A defensible audit basis for a mid-sized government site where the major page templates don't vary widely. If your site has a consistent template structure and the service forms are limited in number, a 50-page sample can be representative.

Full audit (150-200 representative pages): 4 to 6 weeks

For larger government sites with multiple department subsites, varied page templates, a large form inventory, and a significant document library, a 200-page representative sample provides stronger coverage.

Timeline components:

• Site crawl, URL inventory, and representative sample selection: 2-3 days
• Automated scan across full sample: 2-3 days
• Manual keyboard and navigation testing: 5-8 days
• Screen reader testing (NVDA, JAWS, VoiceOver): 5-8 days
• PDF document sample review (50-100 documents): 3-5 days
• Mobile accessibility review (iOS VoiceOver, viewport testing): 2-3 days
• Findings compilation and severity rating: 3-5 days
• Findings report writing and formatting: 3-5 days
• Remediation roadmap prioritization: 1-2 days
• Accessibility statement draft: 1 day
• Internal review and client revision round: 3-5 days

Total: 28 to 45 business days (5 to 9 calendar weeks, accounting for normal project schedule rather than pure working days).

What this gets you: A findings report that covers the major template types, the critical service forms, representative PDF failures, and mobile-specific issues — organized by WCAG success criterion, severity-rated, with specific URLs and code examples. This is the format that supports building a remediation plan directly from the deliverable.

What Affects Audit Duration

Site complexity. A straightforward WordPress CMS site with 8 page templates takes significantly less manual testing time than a custom web application with 30 distinct form types and dynamic content.

Number of distinct page templates. Manual testing time scales with the number of unique interaction patterns, not raw page count. A site with 500 pages but only 10 page templates is easier to test than a site with 100 pages but 40 distinct component types.

Document library size and complexity. PDF review time scales linearly with the number of document types and the age/format of the document inventory. A large library of legacy scanned PDFs takes substantially longer to assess than a library of tagged, structured Word-to-PDF exports.

Third-party integrations. Permit portals, payment systems, GIS tools, and embedded widgets from vendors each require separate testing. Each integration is its own accessibility surface.

Auditor communication and review cycles. A well-scoped engagement with a clear kickoff and an agreed deliverable format completes faster than an engagement that requires scope clarification mid-stream or multiple report revision rounds.

Building the Timeline Backwards from April 2027

The April 26, 2027 deadline is fixed. A realistic planning calendar works backward:

| Milestone | Target Date (working backward from April 2027) | |---|---| | Compliance deadline | April 26, 2027 | | Re-audit complete (verification) | February 2027 | | Critical remediation complete | January 2027 | | All major remediation complete | November 2026 | | Remediation begins | August 2026 | | Audit final report delivered | July 2026 | | Audit begins | June 2026 | | Vendor engagement, scoping, contract | May–June 2026 |

An agency beginning procurement now (May 2026) can realistically complete a full audit by July, begin remediation in August, and reach compliance by February 2027 — with a two-month buffer before the deadline for re-testing and addressing anything missed.

An agency that waits until January 2027 to begin procurement is building a compliance timeline that cannot be completed before the deadline.

What to Ask Before You Engage an Auditor

"How long will the audit take?" is a reasonable first question. The follow-ups:

• "What is included in that timeline — does it include report writing and remediation roadmap, or just the testing phase?"
• "What is your revision process and how does it affect the timeline?"
• "If you find a major issue that requires expanded scope, how do you handle timeline?"
• "When is the latest I can start an engagement with you and still receive a final report by [target date]?"

A credible auditor can answer these directly. Vague answers ("it depends") without qualification are a yellow flag.

Starting Now

The Parallax WCAG audit from Morton Technology Consulting — built specifically for Florida government agencies — is scoped for the timeline above: 200 representative pages, automated and manual testing, NVDA and VoiceOver, full findings report, remediation roadmap, and accessibility statement draft. Current engagements for the 2026 audit cycle are being scheduled now. The sample audit report showing the deliverable format is at morton-digital.com/parallax-sample-audit.

If you are building your own internal readiness assessment before committing to a full engagement, the WCAG Pre-Audit Readiness Kit ($149) includes a self-assessment guide, a procurement RFP template with timeline requirements, and a 49-criterion interactive testing checklist.

---

*Morton Technology Consulting LLC, Tallahassee, FL. Florida government WCAG 2.1 audits. Questions about timeline and scoping: [email protected]*

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →