From the Citizen Engagement & Services edition of November 2, 2026
Route Fifty commentary: with the Title II deadline extended to April 2027, procurement is agencies' key accessibility control; 63% of states require accessibility language in all RFPs
Route Fifty (commentary by Glenda Sims, chief information accessibility officer at Deque Systems) · ADA Title II digital accessibility for state and local services · United States
- Publisher
- Route Fifty
- Original publication
- 2026-11-02
- Source retrieved
- 2026-11-03
What happened
The commentary says agencies covered by Title II are responsible for third-party software and content behind public-facing services, such as payments, e-signatures, scheduling, registration and PDFs. With the DOJ extension, most agencies have until April 26, 2027. It recommends inventorying third-party technology, reviewing contracts, not relying on vendor documentation alone, combining automated and manual testing, and writing testing, remediation timelines and reporting into contracts. It cites a NASCIO 2026 survey finding 63% of states require accessibility language in all RFPs or contract terms, and notes the National Federation of the Blind is suing to undo the extensions.
Why it matters
Portals, payment, permitting and scheduling tools are mostly bought, so Title II compliance for citizen-facing services runs through procurement. The NFB lawsuit could restore earlier deadlines.
Evidence and measured results
Opinion piece by an executive of an accessibility vendor; the NASCIO figure is cited, not reproduced here; no new data.
Limitations and uncertainty
Vendor-affiliated commentary; secondary statistic; legal status of deadlines may change with the NFB case.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-03; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies must make bought software accessible by April 2027 and often do not know what they have.
- Stakeholders
- Procurement officer
- ADA coordinator
- CIO or digital services lead
- City or county attorney
- Discovery questions
- Which third-party tools power resident transactions?
- Do current contracts require accessibility testing and fixes?
- What if the deadline moves earlier?
- Value hypothesis
- An inventory and contract review can focus remediation on the highest-risk vendors; savings are not shown.
- Potential engagement
- A third-party accessibility inventory and contract-language review.
- Unsupported claims
- That the deadline is fixed
- That vendor documentation proves conformance
- Any measured outcome
Pre-sales engineering
Role takeaway
- Fit
- Fits any agency with procured resident-facing software.
- Architecture and integration
- Inventory and test embedded third-party components within public sites and apps.
- Prerequisites
- Vendor and contract list
- Testing tools and manual testers
- Prioritization criteria
- Constraints
- Vendors control fixes
- Deadline uncertainty from litigation
- Security
- Not addressed in the source.
- Proof of value
- End-to-end assistive-technology test of top transactions
- Compare vendor conformance claims with test results
Delivery
Role takeaway
- Work
- Build accessibility into procurement and vendor management.
- Dependencies
- Procurement policy change
- Vendor cooperation
- Testing capacity
- Ownership
- Procurement office with the ADA coordinator.
- Skills and adoption
- Buyers need training on accessibility clauses and evaluating vendor claims.
- Governance checkpoints
- Contract template update
- Renewal accessibility check
- Quarterly vendor-fix tracking
- Acceptance criteria
- Proposed: all new resident-facing contracts include accessibility testing and remediation terms
- Proposed: inventory of third-party components completed by a set date
- Risks
- Missed deadline
- Vendor non-response
- Litigation
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Requires an inventory of third-party components embedded in public-facing sites and apps.
Governance
Who approves, reviews and stays accountable for outcomes?
Contracts should include accessibility requirements, testing, remediation timelines and reporting; vendor claims must be verified.
Security and privacy
What data, permissions and controls need testing?
Not addressed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Calls for usability testing with people with disabilities and notes automated testing alone is insufficient.
Procurement
What should contracts, pricing and exit terms secure?
Renewals and new purchases are the leverage points for requiring accessibility fixes.
Operating model
Which teams own the service once it runs?
Accessibility becomes a standing procurement and vendor-management control.
Publication history
Read preserved resource versions (JSON)Stable resource ID: route-fifty-title-ii-deadline-procurement-commentary-20261102