{"resourceId":"virginia-localities-homepage-accessibility-review-20261025","versions":[{"version":"external-33cbf2bf2d006145c848e723dbd9db11dee74f0eb222a757e4d4419d4b464a51","resource":{"id":"virginia-localities-homepage-accessibility-review-20261025","title":"Review of 35 Virginia localities over 50,000 residents finds every homepage had at least two significant accessibility failures; 51% still use overlays","organization":"Elevage Digital","sector":"Local government web accessibility","geography":"Virginia, United States","publishedAt":"2026-10-25","publicationDate":"2026-10-25","eventDate":"2026-10-23","sourceName":"Elevage Digital","sourceLabel":"Elevage Digital blog","sourceUrl":"https://elevagedigital.com/virginia-title-ii-accessibility-errors/","evidenceClass":"independent-research","outcomeClass":"cautionary","topics":["accessibility-workforce","governance-procurement"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"Most failures are template-level (landmarks, headings, skip links) and shared across a few CMS platforms, so platform or template fixes have wide reach.","governanceImplications":"Few localities name an accessibility coordinator; accessibility statements claim WCAG conformance no homepage met.","securityPrivacyImplications":"Not applicable to this source.","caveats":"Homepages only; limited barrier set; single reviewer; vendor author; barriers framed against WCAG 2.0 while the federal rule uses 2.1 AA.","streamIds":["citizen-engagement"],"roles":{"sales":"This gives a concrete readiness picture: large Virginia localities are not on track for April 2027, and half rely on overlays. The conversation is about template fixes on common CMS platforms, a named coordinator and vendor conformance reports. Keep claims bounded; this is a homepage-only scan by a firm that sells these services.","engineering":"Most failures sit in shared templates: landmarks, heading order, skip links and keyboard menus. With 60% of sites on one CMS vendor, engineering should check whether fixes can be made in platform themes. Proof of value is a before-and-after template test plus full-task testing beyond the homepage.","delivery":"Delivery priorities from the source: fix global templates first, name a coordinator, collect vendor ACRs, train content authors and plan for barriers that will remain past the deadline. Ownership sits with the locality's web lead and ADA coordinator. Proposed acceptance criteria are template-level WCAG 2.1 AA checks and a published coordinator contact. Interpretation."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["Who is the named digital accessibility coordinator?","Which CMS and theme power the site?","Do vendor contracts require accessibility conformance reports?"],"valueHypothesis":"Template-level remediation could clear many repeated failures quickly; not measured here.","potentialEngagement":"A template and top-task accessibility assessment with a deadline plan.","unsupportedClaims":["Full-site compliance status","That overlays caused the failures","Results outside Virginia"]},"engineering":{"fit":"Applies to local government CMS sites, especially on shared platforms.","architectureIntegration":"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.","proofOfValue":["Retest the 10 barrier types after template fixes","Keyboard test of main navigation and search"]},"delivery":{"work":"Remediate templates and set up accessibility governance before April 2027.","dependencies":["CMS vendor","Content authors","Budget"],"ownership":"Web manager with ADA coordinator.","skillsAdoption":"Content author training on accessible content.","governanceCheckpoints":["Coordinator named and published","Template fixes verified","Plan for unresolved barriers"],"acceptanceCriteria":["Proposed: zero template-level failures on retest","Proposed: vendor ACRs collected for key SaaS tools"],"risks":["Deadline slip","Vendor dependency","Content regressions after fixes"]}},"retrievedAt":"2026-10-30T03:09:17Z","enrichedAt":"2026-10-30T03:17:06Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Recommends training staff who create web and social content.","procurementImplications":"Recommends collecting VPAT-based Accessibility Conformance Reports from IT and SaaS vendors, as VITAA requires.","operatingModelImplications":"Calls for named accountability, plans for barriers not fixed by the deadline, and periodic review.","sourceVerification":{"openedUrl":"https://elevagedigital.com/virginia-title-ii-accessibility-errors/","referenceExcerpt":"All of the sites with overlays contain accessibility issues detailed in the Key Findings.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}