WCAG 2.1 Requirements for Government Websites: What Texas Agencies Need to Know Now

The ADA Title II deadline for most Texas government websites has passed. If your agency hasn’t addressed WCAG 2.1 AA compliance, you’re not just at legal risk, you’re locking out constituents who depend on your 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 finalized by the DOJ in 2024, state and local government entities must conform to WCAG 2.1 Level AA. The compliance deadline for entities serving populations of 50,000 or more was April 24, 2026. Special district governments, including workforce boards, mental health authorities, and similar entities, may have until April 26, 2027, but agencies should verify their specific deadline with legal counsel.

The Four WCAG Principles, What They Actually Mean

1. 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.

2. 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.

3. 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.

4. 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. DOJ 2024 guidance is explicit: tools like AccessiBe, UserWay, and similar overlays do not constitute WCAG compliance. They patch surface symptoms without fixing underlying code.
• 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

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.