From the Citizen Engagement & Services edition of October 29, 2026
Review of 35 Virginia localities over 50,000 residents finds every homepage had at least two significant accessibility failures; 51% still use overlays
Elevage Digital · Local government web accessibility · Virginia, United States
- Publisher
- Elevage Digital
- Original publication
- 2026-10-25
- Source retrieved
- 2026-10-30
- Event date
- 2026-10-23
What happened
Between October 18 and 23, 2026, the author reviewed homepages of 35 Virginia localities with over 50,000 residents for 10 barrier types. Every homepage had at least two significant failures, averaging five. 91% had landmark problems, 86% ambiguous links, 80% heading errors, 74% alt-text problems and 57% keyboard-operability issues (up since April). Color contrast issues fell to 29%. 51% use overlays, all with remaining issues. Only 20% name a digital accessibility coordinator as Virginia's VITAA requires.
Why it matters
Fresh measurement of local government readiness six months before the April 26, 2027 federal Title II deadline and six months after Virginia's state law took effect. Shows CMS platform concentration (CivicPlus at 60%) and overlay reliance.
Evidence and measured results
Homepage-only review of 10 barrier types using automated tools plus limited manual testing (keyboard, visual inspection, one PDF per site); follow-up to an April 2026 review. Written by a firm that sells accessibility services.
Limitations and uncertainty
Homepages only; limited barrier set; single reviewer; vendor author; barriers framed against WCAG 2.0 while the federal rule uses 2.1 AA.
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
- Local governments are unlikely to meet WCAG 2.1 AA by April 2027 and many rely on overlays.
- Stakeholders
- County or city web manager
- ADA coordinator
- CMS vendor account manager
- IT procurement
- Discovery questions
- Who is the named digital accessibility coordinator?
- Which CMS and theme power the site?
- Do vendor contracts require accessibility conformance reports?
- Value hypothesis
- Template-level remediation could clear many repeated failures quickly; not measured here.
- Potential engagement
- A template and top-task accessibility assessment with a deadline plan.
- Unsupported claims
- Full-site compliance status
- That overlays caused the failures
- Results outside Virginia
Pre-sales engineering
Role takeaway
- Fit
- Applies to local government CMS sites, especially on shared platforms.
- Architecture and integration
- Fix theme and component templates; add automated checks; plan PDF remediation.
- Prerequisites
- CMS theme access or vendor cooperation
- Testing tools
- Content inventory
- Constraints
- Vendor-controlled themes
- Homepage-only evidence
- Security
- No specific security issues raised by this source.
- Proof of value
- Retest the 10 barrier types after template fixes
- Keyboard test of main navigation and search
Delivery
Role takeaway
- Work
- Remediate templates and set up accessibility governance before April 2027.
- Dependencies
- CMS vendor
- Content authors
- Budget
- Ownership
- Web manager with ADA coordinator.
- Skills and adoption
- Content author training on accessible content.
- Governance checkpoints
- Coordinator named and published
- Template fixes verified
- Plan for unresolved barriers
- Acceptance criteria
- Proposed: zero template-level failures on retest
- Proposed: vendor ACRs collected for key SaaS tools
- Risks
- Deadline slip
- Vendor dependency
- Content regressions after fixes
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?
Most failures are template-level (landmarks, headings, skip links) and shared across a few CMS platforms, so platform or template fixes have wide reach.
Governance
Who approves, reviews and stays accountable for outcomes?
Few localities name an accessibility coordinator; accessibility statements claim WCAG conformance no homepage met.
Security and privacy
What data, permissions and controls need testing?
Not applicable to this source.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Recommends training staff who create web and social content.
Procurement
What should contracts, pricing and exit terms secure?
Recommends collecting VPAT-based Accessibility Conformance Reports from IT and SaaS vendors, as VITAA requires.
Operating model
Which teams own the service once it runs?
Calls for named accountability, plans for barriers not fixed by the deadline, and periodic review.
Publication history
Read preserved resource versions (JSON)Stable resource ID: virginia-localities-homepage-accessibility-review-20261025