INSIGHTS · DIGITAL ACCESSIBILITY
WCAG 2.1 Requirements for Government Websites: What Texas Agencies Need to Know Now
The DOJ has extended the ADA Title II web accessibility deadlines, but the requirement hasn’t changed. State and local government websites must still conform to WCAG 2.1 AA, and the extra year is time to remediate, not a reason to wait. Agencies that haven’t started are also locking out constituents who depend on their services every day.
I’ve spent the last year doing accessibility remediation across Texas workforce boards, mental health authorities, and public agencies. The patterns are consistent: most sites have the same categories of failures, most agencies underestimate what “compliant” actually means, and almost every agency that bought an overlay widget thinks they’re covered. They’re not.
Here’s a plain-language breakdown of what WCAG 2.1 AA actually requires, and what it means operationally for your agency.
What Is WCAG 2.1 and Why Does It Apply to You?
WCAG stands for Web Content Accessibility Guidelines. Version 2.1 is the current enforceable standard, organized into four principles: Perceivable, Operable, Understandable, and Robust, often referred to as POUR.
Under the ADA Title II rule DOJ finalized in 2024, state and local government entities must conform to WCAG 2.1 Level AA. In April 2026, DOJ extended the original compliance dates by one year. Public entities with a total population of 50,000 or more now have until April 26, 2027. Entities with populations under 50,000 and special district governments have until April 26, 2028. Which deadline applies depends on how your organization is structured and which jurisdiction it’s tied to, so confirm yours with legal counsel. The extension also doesn’t pause other obligations. Recipients of federal funds have been covered by Section 504 for decades; workforce boards are covered by WIOA Section 188, and Texas state agencies and universities must already meet state accessibility standards under 1 TAC Chapters 206 and 213.
- 50WCAG 2.1 AA success criteria your site must meet
- 4.5:1minimum color contrast ratio for normal body text
- April 26, 2027new ADA Title II deadline for entities serving 50,000+
The Four WCAG Principles, What They Actually Mean
-
Perceivable
Users must be able to perceive all content. In practice: every image needs descriptive alt text, every video needs captions and audio descriptions, text must have sufficient color contrast (4.5:1 for normal text, 3:1 for large text), and content can’t rely solely on color to convey meaning.
-
Operable
Every function must be operable by keyboard alone, no mouse required. Navigation must be consistent and skippable. No content should flash more than three times per second. Users must have enough time to read and use content.
-
Understandable
Text must be readable and the page language must be identified in the HTML. Navigation must behave predictably. Forms must have clear labels, and errors must be identified and described, not just highlighted in red.
-
Robust
Content must work with current and future assistive technologies. This means valid, well-formed HTML with proper use of ARIA roles, states, and properties. Screen readers, switch access devices, and voice control software all depend on this layer being correct.
“The agencies that get hit with complaints aren’t the ones who tried and fell short. They’re the ones who bought an overlay widget and stopped thinking about it. That’s not a compliance strategy, that’s a liability.”
— Janie Martinez Gonzalez, CEO, Webhead
What WCAG 2.1 AA Does NOT Allow
- Overlay widgets as a compliance substitute.Tools like AccessiBe, UserWay, and similar overlays patch surface symptoms; they don’t make a site WCAG compliant. Accessibility advocates and courts have consistently found that overlays don’t fix the underlying code, and DOJ’s rule measures compliance against WCAG itself, not against any tool.
- PDFs as the primary content format.PDFs require separate accessibility remediation. High-demand content must be available in accessible HTML.
- Images of text.Text embedded in images cannot be read by screen readers. Content must be live text.
- Auto-playing media without controls.Audio or video that plays automatically without a way to pause or stop it fails WCAG.
- Forms without proper labels.Every input field must have a programmatically associated label, placeholder text alone does not qualify.
Common Failures We See on Texas Government Sites
- Missing or generic alt text on images (“image001.jpg” is not descriptive)
- Insufficient color contrast, particularly on agency-branded color schemes with light gray text
- PDFs that are scanned images rather than tagged, readable documents
- Navigation menus that are not keyboard accessible
- Forms with unlabeled fields or error messages that only use color
- Video content without captions (auto-generated captions don’t meet the standard)
- Heading structure that skips levels or uses headings purely for visual styling
- Tables without proper headers and scope attributes
Frequently Asked Questions
What is WCAG 2.1 AA and is it required for government websites?
WCAG 2.1 AA is the technical standard for web accessibility. Under DOJ’s 2024 ADA Title II rule, as amended in April 2026, state and local government entities with populations of 50,000 or more must comply by April 26, 2027. Smaller entities and special district governments must comply by April 26, 2028. Compliance means meeting all Level A and Level AA success criteria in WCAG 2.1.
Does an accessibility overlay widget make my site WCAG compliant?
No. Accessibility advocates and courts have consistently found that overlays don’t fix the underlying code, and DOJ’s rule measures compliance against WCAG itself, not against any tool. Agencies relying solely on overlays remain at legal risk. Proper remediation requires fixing the underlying HTML, CSS, and content, not layering a script on top of it.
How long does WCAG remediation take for a government website?
A focused Phase 1 remediation covering highest-traffic pages typically runs 30–60 days. Full site remediation for a medium-complexity government website generally takes 60–120 days. The starting point is always an accessibility audit to scope the actual work.
Can Webhead access our site under a Texas DIR contract?
Yes. Webhead holds Texas DIR contracts CPO-5021 and CPO-5218, which cover web accessibility remediation and digital compliance services. Eligible agencies can engage directly, no RFP required.
How to Get Started
The first step is always an honest audit, not a tool scan, not a checkbox exercise. A real audit looks at your highest-traffic pages, your forms, your documents, your navigation, and your media. It identifies what’s broken, prioritizes by risk and user impact, and gives you a scoped remediation plan you can actually execute.
We’ve done this work across Texas. We know the patterns, we know what compliance documentation protects you if you’re ever audited, and we know how to build accessible sites that stay accessible when your team updates content.
Start With an Accessibility Audit
Available under Texas DIR contracts CPO-5021 and CPO-5218. No RFP required.
Request an Audit