The DOJ Final Rule (2024) under ADA Title II has placed public entities in a challenging position: you're now responsible for the accessibility of every digital tool a vendor operates on your behalf. If your parking payment app, online permitting system, or constituent communication platform fails to meet WCAG 2.1 Level A or AA requirements, it's your compliance deadline Assistive Technology risk, not just the vendor's reputation.
The decision isn't whether to act; it's whether to invest in remediating the tool you have or replacing it with one that already conforms.
The Decision You Are Facing
You've identified a third-party system that doesn't meet WCAG 2.1 A and AA. Your procurement contract may predate the rule's publication in April 2024, but that doesn't exempt you from the compliance timeline. Public entities serving populations of 50,000 or more face an April 2027 deadline; smaller jurisdictions and special district governments have until April 2028.
Now you need to decide:
- Remediate: Work with your current vendor to bring the tool into conformance.
- Replace: Terminate the contract and procure an accessible alternative.
- Hybrid: Remediate critical paths while planning a phased replacement.
Each path carries different risk profiles, cost structures, and timeline implications.
Key Factors That Affect Your Choice
Vendor cooperation and capability. Does your vendor acknowledge the accessibility gaps? Have they committed to a remediation timeline that fits within your compliance deadline? Some vendors will produce a roadmap within 30 days. Others will claim accessibility is "on the roadmap" with no enforceable commitment. If your vendor cannot demonstrate WCAG expertise or provide evidence of past conformance work, remediation becomes a high-risk bet.
Contractual leverage. Review your existing agreement for accessibility representations, indemnification clauses, and termination rights. If the contract includes an accessibility warranty that the vendor is now breaching, you may have grounds for cost-free termination or mandated remediation Assistive Technology the vendor's expense. If the contract is silent on accessibility, your leverage is limited to renewal negotiations or the threat of non-renewal.
Criticality of the service. A parking payment app affects convenience. A voting registration system affects constitutional rights. The DOJ Final Rule (2024) acknowledges that some conformance gaps have "minimal impact on access" if individuals with disabilities can use the experience as effectively as those without disabilities. But if your tool gates access to essential civic participation, partial conformance isn't a defensible position.
Volume of violations and remediation complexity. Run a conformance test using both automated tools and manual screen reader evaluation. If you're seeing 15 WCAG violations concentrated in a single user flow, remediation may be straightforward. If you're seeing 200+ violations across dynamic content, form validation, and third-party embeds, you're looking Assistive Technology architectural problems that a vendor may not be equipped to solve within your timeline.
Market alternatives. Research whether accessible alternatives exist in your category. For some government technology markets, particularly niche permitting or case management systems, you may find that no vendor offers full WCAG 2.1 AA conformance out of the box. In that scenario, remediation is your only path, and you'll need to build in time for iterative testing and re-testing.
Path A: Remediate When the Vendor Can Deliver
Choose remediation when:
- Your vendor has demonstrated WCAG expertise and provides a detailed remediation plan with milestone dates Assistive Technology least six months before your compliance deadline.
- The contract includes enforceable accessibility commitments or you have leverage to amend it.
- Conformance testing reveals a manageable scope of violations (typically fewer than 50 unique issues).
- Replacing the tool would disrupt critical operations or require costly data migration.
- The vendor agrees to provide an Accessibility Conformance Report documenting conformance upon completion.
Require monthly progress reports. Insist on access to the vendor's testing environment so your team can validate fixes before they reach production. Build in a contractual off-ramp: if the vendor misses two consecutive milestones, you retain the right to terminate without penalty and recover transition costs.
Document everything. If the vendor's remediation ultimately fails and you face DOJ enforcement, you'll need evidence that you took reasonable steps to achieve conformance and that the vendor's performance, not your inaction, caused the delay.
Path B: Replace When Remediation Risk Is Too High
Choose replacement when:
- The vendor cannot or will not commit to a remediation timeline that meets your deadline.
- Conformance testing reveals systemic architectural barriers (inaccessible JavaScript frameworks, non-semantic HTML, missing ARIA landmarks across the entire application).
- The contract is approaching renewal and you have budget authority to initiate a new procurement.
- Accessible alternatives exist in the market and you can complete procurement, migration, and testing within 18 months.
- The tool is not mission-critical and you can manage a transition without service disruption.
Start your procurement process immediately. Build WCAG 2.1 A and AA conformance into your RFP as a mandatory requirement, not a scored criterion. Require vendors to submit an Accessibility Conformance Report based on the Voluntary Product Accessibility Template and validate their claims through your own testing during the evaluation phase.
Plan for a parallel run period where both the old and new systems operate simultaneously. This gives you time to identify conformance gaps in the new tool before you fully decommission the non-conformant system.
Path C: Hybrid Approach for Complex Portfolios
Choose a hybrid approach when:
- You manage multiple third-party tools with varying levels of conformance.
- Some tools are contractually locked in while others are approaching renewal.
- You have budget constraints that prevent replacing everything Assistive Technology once.
Triage your portfolio by risk and criticality. Remediate tools where the vendor is cooperative and the scope is manageable. Replace tools where remediation is unlikely to succeed within your timeline. For lower-risk tools that affect fewer constituents, document a prioritization plan that demonstrates you're addressing the highest-impact barriers first.
The DOJ Final Rule (2024) allows some flexibility: you're not required to achieve 100% conformance Assistive Technology all times if violations have minimal impact on access. But "minimal impact" is a legal standard you'll need to defend if challenged. Don't rely on this exception as a long-term strategy.
Summary Matrix
| Factor | Remediate | Replace | Hybrid |
|---|---|---|---|
| Vendor cooperation | High: committed timeline | Low: no commitment | Mixed across portfolio |
| Conformance gap | <50 violations, fixable | Systemic architecture issues | Varies by tool |
| Contractual position | Strong leverage or warranty | Approaching renewal | Mixed contract states |
| Timeline pressure | 18+ months to deadline | 24+ months to deadline | Staggered deadlines |
| Service criticality | Moderate impact | High impact or low tolerance for risk | Prioritized by impact |
| Market alternatives | Limited or costly | Accessible options available | Some categories, not all |
The DOJ Final Rule (2024) makes one thing clear: "provides or makes available" means you own the conformance outcome, regardless of who built the tool. If your vendor can't meet WCAG 2.1 A and AA within your compliance window, waiting is not a strategy. It's a liability.
