What A Roadmap Should Do
A roadmap should separate discovery, audit, remediation, retesting, documentation, monitoring, and governance. Those are different workstreams even when one provider helps with several of them.
It should start with the user paths that create the most risk or value: checkout, forms, booking, account access, product discovery, documents, support, and any pages named in a demand letter or lawsuit.
It should make ownership visible. Code fixes, content edits, PDF/file remediation, third-party app decisions, accessibility statement updates, VPAT/ACR evidence, and ongoing monitoring often belong to different people.
How To Phase 30/60/90 Days
Days 0-30 should stabilize evidence, run a public-page snapshot, confirm critical paths, fix obvious blockers, and scope manual review. Legal-pressure situations should stay counsel-first.
Days 31-60 should turn findings into tickets, remediate templates and repeated components, address documents and media, and prepare retest evidence.
Days 61-90 should retest, update the accessibility statement, document unresolved limitations, set monitoring cadence, and decide whether ongoing provider support, accessFlow-style workflow, accessServices-style managed help, VPAT/ACR support, or file accessibility is needed.
How To Use The Generated Plan
Use the generated roadmap in a team meeting, agency handoff, provider call, or counsel-coordinated technical discussion. It is a planning artifact, not a legal opinion or compliance certificate.
Attach a public-page snapshot if you want follow-up. The saved lead then includes the roadmap context, urgency, platform, workstreams, and consent choices so the follow-up is more useful.
If the plan points toward provider help, compare provider categories with the scorecard before sharing details with a partner.
Where accessiBe May Fit
When appropriate and with your consent, we may refer you to accessiBe. Its public offerings include accessWidget, accessFlow, accessServices, VPAT/ACR support, expert audit, user testing, file/PDF accessibility, and select-plan litigation support resources.
The roadmap helps decide whether the next conversation should focus on quick public-page evidence, developer workflow, managed services, procurement documentation, file accessibility, litigation-support resources, or maintenance.
Decision path
Use these links to move from research to evidence, then from evidence to a responsible remediation option.
Frequently asked questions
Can I use the roadmap without submitting my email?
Yes. The planner runs in your browser and shows the roadmap on the page. Submitting a URL and work email is optional and only needed if you want to attach the roadmap to a public-page snapshot and follow-up.
Does the roadmap prove compliance?
No. It organizes technical work, owners, evidence, and next steps. It is not legal advice, a certification, a VPAT, or a WCAG conformance statement.
When should I involve a provider?
Involve a provider when the roadmap shows manual audit needs, limited internal implementation capacity, document/file scope, procurement evidence, litigation pressure, or ongoing maintenance needs that your team cannot own alone.