Accessibility Is Not a Feature We Added. It's the Foundation We Built On.
Every government website platform claims to support accessibility. Most mean they passed an automated scan once, two years ago. WPPersona means WCAG 2.1 AA compliance is the specification every component was designed to · not a checklist applied after the fact.
The DOJ Has Spoken. Vague Intentions Are No Longer Enough.
The Department of Justice published its final rule on web accessibility for state and local government under Title II of the ADA. The rule requires WCAG 2.1 Level AA compliance · with specific, binding deadlines tied to population size. Aspirational policy statements and checkboxes are no longer sufficient.
April 26, 2027
Government agencies serving 50,000 or more residents must have all web content meeting WCAG 2.1 AA by this date.
April 26, 2028
Government agencies serving under 50,000 residents must have all web content meeting WCAG 2.1 AA by this date.
What the rule covers
- Web content · all pages, navigation, and digital services
- PDFs and other document formats hosted on the site
- Online services · permit portals, payment systems, forms
- Third-party tools embedded into government web properties
What it doesn't excuse
- "Our vendor is responsible for accessibility"
- "We passed an automated scan last year"
- "We don't have budget for accessibility remediation"
Compliant Templates. Compliant Components. Compliant Workflows.
Accessibility cannot be bolted on after a platform is built. It has to be the constraint that shapes every design decision, every component API, every editorial workflow. That's the only way compliance holds across a full content lifecycle.
Templates & Themes
Every template ships with contrast-tested color palettes, properly scaled typography ratios, and logical reading order enforced in the HTML structure · not applied as a post-processing step.
Component Library
Every UI component is tested against WCAG 2.1 success criteria, ARIA Authoring Practices Guide patterns, full keyboard operability, and all major screen readers: NVDA, JAWS, VoiceOver, and TalkBack.
Content Editing Workflow
Alt text is required before images can be published. Heading levels are validated in real time. Color contrast is checked inline. PDF risk scores surface in the document library before files go live.
Automated Monitoring
Weekly accessibility scans run across every page. A compliance dashboard aggregates results by department and issue type. Teams receive notifications before a citizen encounters a broken experience.
Your Procurement Office Will Ask for This. We're Ready.
Government procurement processes require formal accessibility documentation before a vendor can be approved. WPPersona maintains the complete set of compliance artifacts · updated on a regular schedule, available immediately upon request.
VPAT / ACR
Voluntary Product Accessibility Template and Accessibility Conformance Report, updated twice per year and publicly available · no NDA required.
Accessibility Statement
Published and maintained for the platform. A generator-assisted tool creates a customized statement for each agency site · ready for your footer on day one.
WCAG 2.1 AA Self-Assessment
A full success-criteria self-assessment mapping our platform against all Level A and Level AA requirements. Available on request for procurement review.
SOC 2 Type II Report
Available under NDA for security procurement reviews. Covers security, availability, and confidentiality trust service criteria over a 12-month observation period.
See Your Agency's PDF Risk in 2 Minutes
Enter your government website URL. We crawl every page, scan every PDF, and deliver a full ADA compliance risk report. No account. No credit card.
Run Free AuditTalk to Someone Who Speaks Government
Our team understands government procurement, ADA compliance timelines, and what it takes to migrate a government website. Free 20-minute demo. No hard sell.
- Full platform walkthrough for your agency type
- Answers to procurement and security questions
- Honest timeline and migration assessment