From the Citizen Engagement & Services edition of October 29, 2026
Accessibility researchers find overlays on U.S. state government websites failed to fix core barriers and sometimes broke functionality; overlay use fell from seven to five states by October 2026
Alison Walden and Matt Vitale (Publicis Sapient), published by Law Office of Lainey Feingold · State government web accessibility · United States (state government websites)
- Publisher
- Law Office of Lainey Feingold (LFLegal)
- Original publication
- 2026-10-28
- Source retrieved
- 2026-10-30
What happened
In a 2025 study of U.S. state government websites, seven states used overlays from five companies. Tested overlay features did not fix the most common barriers: keyboard and screen-reader navigation failures, unclear links, missing form labels and inaccessible PDFs. Some features reduced contrast, broke a carousel, disabled buttons or links, and one overlay could not be reached by keyboard. A recheck in October 2026 found five of the seven states still using overlays and no new adopters.
Why it matters
Directly relevant to state and local governments preparing for the ADA Title II web rule deadline of April 26, 2027 for entities of 50,000 or more: overlays are not a compliance path, and budget should go to code-level remediation and accessible process.
Evidence and measured results
Expert manual testing of overlay features on state sites with assistive technology; findings described qualitatively with examples. No per-site scores published in the article. Authors work at a digital consultancy; the publisher is an accessibility lawyer who opposes overlays.
Limitations and uncertainty
Qualitative; authors and publisher have known positions; state sites only; overlay vendors were not quoted.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Governments facing the Title II deadline may spend on overlays that do not remove barriers.
- Stakeholders
- State or local web services director
- ADA coordinator
- Procurement
- Disability advocates
- Discovery questions
- Is the site using an overlay, and what does it cost?
- Which resident tasks fail with a keyboard or screen reader?
- How many service documents exist only as PDFs?
- Value hypothesis
- Shifting overlay spend into template remediation and testing could remove more barriers per dollar; not measured here.
- Potential engagement
- An accessibility assessment of top resident tasks with a remediation roadmap.
- Unsupported claims
- That removing overlays alone improves accessibility
- Compliance by April 2027
- Overlay effects on local government sites specifically
Pre-sales engineering
Role takeaway
- Fit
- Applies to any public website or portal with overlay scripts or legacy templates.
- Architecture and integration
- Fix shared templates and components; add automated and manual accessibility testing to CI; remediate PDFs.
- Prerequisites
- Inventory of templates and PDFs
- Assistive technology test capability
- CMS access
- Constraints
- Vendor-hosted CMS limits code changes
- Large PDF backlogs
- Security
- Check whether overlays collect disability profile data.
- Proof of value
- Screen-reader and keyboard test of top tasks with and without the overlay
- Count WCAG failures fixed at template level
Delivery
Role takeaway
- Work
- Move from overlay reliance to a remediation-based accessibility program.
- Dependencies
- CMS vendor cooperation
- Accessibility specialists
- Content authors
- Ownership
- Digital services lead with ADA coordinator.
- Skills and adoption
- Author training on headings, links, alt text and accessible documents.
- Governance checkpoints
- Baseline audit
- Template fixes verified
- Recurring manual testing
- Acceptance criteria
- Proposed: top resident tasks pass keyboard and screen-reader testing
- Proposed: overlay removed only after template fixes are verified
- Risks
- Deadline pressure leading to shortcuts
- PDF backlog
- Vendor platform limits
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?
Accessibility has to be fixed in templates, components and content; a client-side overlay cannot repair underlying markup.
Governance
Who approves, reviews and stays accountable for outcomes?
Accessibility should be built into planning, design, content and development, with specialists and disabled users involved.
Security and privacy
What data, permissions and controls need testing?
One overlay asked users to choose a disability profile, which raises data sensitivity questions; otherwise not addressed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Calls for investment in skilled accessibility staff and people with disabilities on teams.
Procurement
What should contracts, pricing and exit terms secure?
Agencies paying for overlays may be buying a product that does not deliver compliance.
Operating model
Which teams own the service once it runs?
Sustained accessibility needs process ownership rather than a plug-in.
Publication history
Read preserved resource versions (JSON)Stable resource ID: state-gov-website-accessibility-overlays-study-update-20261028