2026-05-17 · 8 min read

Harris County Texas Government Website Accessibility: Houston, HISD, METRO, and the April 2027 DOJ Title II Deadline

# Harris County Texas Government Website Accessibility: Houston, HISD, METRO, and the April 2027 DOJ Title II Deadline

Harris County is the third most populous county in the United States. At approximately 4.7 million residents, it is larger than 26 individual U.S. states. ^[2] Within that population, Harris County government and the City of Houston government are separate legal entities — each independently responsible for bringing their digital properties into WCAG 2.1 Level AA conformance by April 26, 2027. ^[1]

Houston ISD, Houston Community College, the Metropolitan Transit Authority of Harris County (METRO), the Harris County Flood Control District, and the University of Houston System are each additional independently covered public entities — each with their own compliance deadline and their own compliance obligation.

This post gives Harris County IT directors and agency heads the specific compliance picture for each covered entity, the particular risks created by Harris County's linguistic diversity, and what a defensible compliance program looks like.

The Covered Entities

Harris County government — The Harris County Commissioners Court and all county agencies and departments. Harris County's digital footprint includes the county's main website, the Tax Assessor-Collector, the County Clerk, the District Clerk, the Sheriff, the Constables, Precinct websites, and numerous specialized department portals. The county serves a population of approximately 4.7 million. The April 26, 2027 deadline applies. ^{[1] [2]}

City of Houston — A separately incorporated government serving approximately 2.3 million residents. The city's digital footprint includes the main houston.gov website, the 311 service portal, the public works permit system, the Houston Police Department site, the Houston Fire Department, the public library system, and dozens of department-specific web properties and applications. ^[3]

Houston ISD — One of the largest school districts in the United States, serving approximately 175,000 students across more than 270 campuses. HISD's digital properties include its main website, the parent information portal, student registration systems, employee portals, cafeteria payment systems, and the library catalog — all of which must meet WCAG 2.1 AA. The April 26, 2027 deadline applies at HISD's enrollment scale. ^[6]

Houston Community College — A public community college district serving approximately 70,000 credit and non-credit students. HCC's digital properties include its main website, student registration and financial aid systems, learning management system integrations, course catalogs, and the library portal. As a public institution, it is an independently covered entity. ^[7]

Metropolitan Transit Authority of Harris County (METRO) — The regional transit authority serving the Greater Houston area. METRO's compliance obligation extends to its main website, the trip planning tool, the METRO mobile app, schedule and route PDFs, rider alert systems, and real-time arrival information interfaces. All must meet WCAG 2.1 AA. ^[8]

Harris County Flood Control District — An independently organized special district managing flood infrastructure across Harris County. The Flood Control District's digital properties include its public website, flood alert notification systems, project information pages, and permit portals. As a Title II entity, it faces the April 2027 deadline. ^[11]

University of Houston System — A public university system including UH main campus (46,000+ students), UH-Clear Lake, UH-Downtown, and UH-Victoria. Public universities are independently covered entities. The UH System's compliance obligation extends across all campuses and their respective digital properties. ^[12]

The Linguistic Diversity Problem

Harris County is the second most linguistically diverse county in the United States. More than 145 languages are spoken. Approximately 43.7% of Harris County residents speak a language other than English at home. ^[4]

This creates a compounded access barrier that is specific to Harris County and a small number of other highly diverse jurisdictions: residents who are both limited English proficient and disabled face a double barrier when government digital services are inaccessible.

WCAG 2.1 Level AA Success Criterion 3.1.1 requires that the primary language of each web page be programmatically determinable — a basic requirement that allows screen readers to switch pronunciations correctly. When a page presents content in Spanish but the lang attribute identifies English, the screen reader mispronounces every Spanish word. ^[9] This is one of the 17% of pages flagged by the WebAIM Million for missing document language — a failure that disproportionately harms the large share of Harris County's population that is both linguistically diverse and using assistive technology.

For a county where county services reach across language communities, the intersection of language access and disability access is not a niche concern. It is a front-line equity issue.

What Is Covered

The rule covers web content and mobile apps that a public entity makes available to the public or uses to offer services, programs, or activities. For Houston-area entities, that includes: ^[5]

• Main government websites and all subdomains
• Web-based service portals: permit systems, utility payment, licensing, registration, benefit applications
• Mobile apps distributed to the public
• Documents published through any of the above: PDFs, Word files, spreadsheets, presentations
• Third-party systems procured by the agency — if you contracted for a vendor-built permit portal, that portal must meet WCAG 2.1 AA

The most commonly overlooked category is documents. Harris County government entities publish massive volumes of PDFs: meeting agendas and minutes, budget documents, ordinances, court filings, emergency management documents, permit applications, flood control project updates, and financial reports. Most of these PDFs are not accessible. ^[13]

Scanned-image PDFs — where a physical document was scanned and saved as an image — are completely inaccessible to screen readers. They contain no machine-readable text. NVDA or JAWS reads them as blank documents.

Digitally created PDFs that were never tagged are also inaccessible: no reading order, no heading structure, no alt text for charts, no accessible form fields. Creating a tagged, accessible PDF requires explicit effort during document creation and is not a default output of most government document workflows.

The Five Most Common WCAG Failures on Government Sites

The WebAIM Million 2024 report found that 95.9% of home pages had detectable WCAG 2 failures, with the five most common being: ^[10]

1. Low contrast text (81.0%) — Text that does not meet the 4.5:1 contrast ratio requirement for normal text or 3:1 for large text. Common in government sites that use light gray text on white backgrounds, colored text on colored backgrounds, or watermarked content.

2. Missing alt text for images (54.5%) — Images that convey information without alternative text. Charts, maps, infographics, scanned document images, and photos with informational captions are the most common failures on government sites.

3. Missing form labels (48.6%) — Form fields without programmatically associated labels. A field labeled visually by a nearby text element but not connected with a for attribute or aria-labelledby is invisible to screen readers.

4. Empty links (44.6%) — Links that contain no text or whose text content is not descriptive. Icon links (PDF download icons, social media buttons), image-only links without alt text, and "click here" links that give no context are all failures.

5. Missing document language (17.1%) — Pages without a lang attribute on the <html> element. Particularly damaging in linguistically diverse contexts.

These five failures are detectable by automated scanners. The remaining 43% of WCAG failures — navigation traps, focus management problems, inaccessible custom widgets, timing issues — require manual testing with actual assistive technology such as NVDA, JAWS, or VoiceOver to identify.

Texas State Law Context

Texas Government Code Chapter 2054, Subchapter M requires Texas state agencies to make their electronic and information resources accessible. The Texas Department of Information Resources (DIR) oversees this requirement and publishes accessibility standards and technical guidance. ^[14]

For Houston-area entities, the federal DOJ Title II rule and the Texas EIR accessibility framework are substantively aligned — both require WCAG 2.1 AA-level conformance. State agencies must meet both; local government entities (counties, cities, ISDs, transit authorities, community colleges) are primarily subject to the federal rule.

The practical takeaway: the compliance target is the same regardless of which legal authority a Houston-area entity is more directly subject to.

A Realistic Compliance Program

A compliance program for a large government entity like Harris County or the City of Houston has more moving parts than for a small municipality — but the structure is the same:

Scope the digital footprint. Before any testing, understand what must comply. For Harris County or Houston city, that means inventorying dozens of subdomains, dozens of third-party-built applications, years of published PDFs, and mobile apps. This inventory step is frequently underestimated. Expect it to take four to eight weeks for a large entity.

Commission an audit. An automated scan is not a WCAG audit. Automated tools detect approximately 57% of WCAG failures. The remaining issues require manual testing with assistive technology — keyboard navigation, screen reader testing, zoom and reflow testing, and review of complex interactions. A credible audit of a large government entity will include both automated and manual testing components.

Prioritize by service impact. Not all failures are equal. A permit portal that blocks residents from applying for construction permits is more urgent than a formatting issue on an archived historical document. Remediation prioritization should be driven by the severity of the access barrier and the volume of residents affected.

Fix procurement going forward. Every new technology contract is an opportunity to prevent future accessibility debt. Contracts executed after your compliance date should require WCAG 2.1 AA conformance, specify testing methodology, and include remediation obligations if the vendor's deliverable fails.

Publish an accessibility statement. The DOJ expects covered entities to have a mechanism for residents to report accessibility barriers and to receive a response. This does not require perfection; it requires a demonstrated compliance process.

Next Steps for Harris County

The April 26, 2027 deadline is eleven months away. For entities the size of Harris County government and the City of Houston, commissioning an audit now gives enough time to complete remediation before the deadline — but only if the process begins soon. Entities that wait until mid-2026 will not have enough time for full remediation.

For context on the broader Texas compliance picture, see Texas government website accessibility, which covers all 254 Texas counties, the state's major transit authorities, ISDs, and community college districts.

For comparison with another highly diverse large-county compliance picture, see Florida government website accessibility.

For other Texas county compliance guides as they become available:

• Dallas County Texas government website accessibility
• Bexar County Texas government website accessibility

This post is informational and does not constitute legal advice. Each government entity should consult with qualified legal counsel regarding its specific compliance obligations.

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →