We just developed a plan for a state government project to fast track ADA compliance and we can help you too. In fact, here’s the exact project flow we recommend for becoming compliant with the ADA Title II web rule by April 24, 2026.
| Step | Phase | What Happens | Output / Deliverable |
|---|---|---|---|
| 1 | Requirements | Confirm what requirements are in place (ADA Title II Web Rule, State or Local policies, WCAG 2.1 AA or 2.2 AA). | Share requirements baseline for the project team |
| 2 | Inventory + Ownership | Validate web properties inventory, identify system owners, and confirm what systems and content are in scope. | Confirmed inventory + owners + scope boundaries |
| 3 | Prioritization | Rank properties, key workflows, high-traffic pages, high-risk content, and high-impact documents so the most important items get handled first. | Prioritized audit + remediation plan |
| 4 | WCAG Audits (Web Properties) | Conduct desktop + mobile audits for the web properties. | Audit findings with issues, severity, and recommendations |
| 5 | Document Remediation (Start Immediately) | Begin remediating documents (PDFs, Word, Excel, spreadsheets) without waiting for web audits to finish. | Remediated documents ready for use/public access |
| 6 | Remediation (Web Properties) | Fix accessibility issues as audits complete (code fixes and content fixes). | Implemented remediation across prioritized assets |
| 7 | Validation (Post-Fix Verification) | Re-test remediated items to confirm fixes actually work and meet WCAG 2.2 AA expectations. | Validation results confirming issue closure |
| 8 | Archived Content Handling | Archive eligible legacy content and publish an accessible request mechanism for users who need an accessible version. | Archived content section + request workflow |
| 9 | Policy Development (Parallel Track) | Develop a digital accessibility policy so compliance becomes sustainable and repeatable long-term. | State web accessibility policy draft/final |
| 10 | Training (Parallel Track) | Create training materials and deliver training for both technical and non-technical staff. | Training content + delivered sessions |
| 11 | Support Documentation (Handoff) | Provide maintenance guidance so the State can sustain compliance after the project. | Long-term support + maintenance documentation |
| 12 | User Testing (Final Evidence Layer) | Screen reader user testing by professionals who are blind or visually impaired to confirm real usability and strengthen defensibility. | User testing results + documented evidence |
| Ongoing | Weekly Reports + Coordination + PM | Provide weekly updates, coordinate with vendors, manage dependencies, and keep delivery moving efficiently. | Weekly status reports + managed execution |
Step 1: Requirements
Before you audit anything, confirm what you’re measuring against. ADA Title II, your state’s policies, and WCAG 2.2 AA. Get everyone aligned on the standard before you start finding issues.
Step 2: Inventory and Ownership
Validate your property list. For each property, identify:
- Who owns the content?
- Who owns the code?
- What vendor (if any) controls the system?
- What’s the document volume?
Step 3: Prioritize
Not all pages and properties are equal. Prioritize by:
- Public-facing vs. internal
- High-traffic pages and key user workflows
- High-risk content (forms, applications, transactions)
- High-volume documents
You can’t fix everything at once. Know what matters most.
Step 4: Accessibility Audits
Conduct desktop and mobile audits for each web property. You need real audits that are 100% manual, not automated scans.
Step 5: Document Remediation
Don’t wait for web audits to finish before touching documents. PDF and document remediation is time-consuming. Start it on day one as a parallel track.
Step 6: Remediation (Web Properties)
Fix accessibility issues as audits complete. This includes both code fixes (HTML, ARIA, keyboard handling) and content fixes (alt text, link text, captions). Work through your prioritized list.
Step 7: Validation
Re-test remediated items to confirm fixes actually work and meet WCAG 2.2 AA. Don’t assume a fix worked—verify it.
Step 8: Archived Content
Archive eligible legacy content and publish an accessible request mechanism for users who need an accessible version of archived materials.
Step 9: Policy Development
Develop a digital accessibility policy so compliance becomes sustainable and repeatable long-term. This doesn’t depend on remediation being complete—start it early.
Step 10: Training
Create training materials and deliver training for both technical and non-technical staff. If your team doesn’t know how to maintain accessibility, you’ll be back in the same position next year.
Step 11: Support Documentation
Provide maintenance guidance so the agency can sustain compliance after the project ends. Document workflows, responsibilities, and ongoing monitoring processes.
Step 12: User Testing
Screen reader testing by real users — professionals who are blind or visually impaired — provides evidence that your remediation actually works in the real world. This is your strongest defensibility layer.
Concurrent Work
The bullet points below run concurrently with other work.
- Weekly reporting
- Vendor coordination
- Project management
- Policy development
- Training development and scheduling
Build these into your plan to start as soon as they make sense.
Accessibility Tracker
Accessibility Tracker is our platform that we built to streamline accessibility projects. Tracker not only helps complete projects faster, it helps you keep track of progress and provides more documentation of your efforts.
Some Tracker highlights:
- Audit-based for full WCAG conformance (not scan-based for 100% score on a scan)
- Assign issues to team members
- Issue tracking from audit finding through remediation and validation
- Reporting that you can share with leadership without rebuilding slides every week
- Evidence collection for audit trails and legal defensibility
It’s built for the way government accessibility projects actually work — multiple properties, multiple project participants, and AI tools to help issues get fixed faster and right the first time.
Key Takeaways
Three months is a condensed time frame, but it’s possible — even for large state government projects.
The keys to meeting the April 24, 2026 deadline are:
- organization
- alignment
- expertise
If you’re ready to get your project started right away, we have a partner with contracts and logistics already in place so we can immediately get to work. We invite you to send us a message below or contact us and we’ll reply back right away.
