2026-05-18 · 6 min read

City of Amarillo, TX — WCAG 2.1 AA Compliance and the April 2027 DOJ Title II Deadline

City of Amarillo, Texas — population 200,000+ [2] — operates amarillo.gov as its primary public-facing digital presence. With the DOJ Title II Final Rule compliance deadline of April 26, 2027 now under 11 months away, we audited the amarillo.gov homepage directly from its live HTML to understand what accessibility barriers city residents currently face.

We found 1 verified Level A failure. Each one is documentable under 28 CFR § 35.200 and each one creates a demonstrable barrier for residents who rely on assistive technology to access city services.

The DOJ Title II Deadline for City of Amarillo

The DOJ Title II Final Rule — extended by interim final rule on April 20, 2026 [1] — requires every covered state and local government entity to bring its public-facing web content into conformance with WCAG 2.1 Level AA. The rule covers the city's main website, department portals, online forms, PDFs, and third-party platforms operated on the city's behalf [3].

With a population of 200,000+, City of Amarillo is above the 50,000-resident threshold and faces the earlier of the two compliance dates: April 26, 2027. The rule does not require perfection on day one — it requires a good-faith compliance program with documented remediation. But it does require that covered entities have identified their failures and are actively remediating them. The time to begin that work is now.

According to WebAIM's 2024 analysis of the top 1,000,000 home pages, 95.9% had detectable WCAG 2 failures [4]. Government websites consistently outpace the general web in accessibility failure rates. The failures we found on amarillo.gov are representative of what we see across government websites of this size — fixable, documented, and addressable within the remaining timeline.

Verified WCAG Failures on amarillo.gov

Every finding below was verified from the live homepage DOM — not from an automated scan estimate, not from training data. We fetched the actual page source and checked each element against its relevant WCAG 2.1 success criterion.

Finding 1: Homepage has no H1 element — heading structure starts at H2 (SC 1.3.1, Level A)

The amarillo.gov homepage contains H2 and H3 headings but no H1. For blind and low-vision residents using screen readers, the H1 is the structural anchor that identifies the page. Without it, a screen reader user navigating by heading encounters Amarillo's homepage as a sequence of sub-headings with no structural context.

Fix: Add a single descriptive H1 to the homepage — visible or visually hidden — identifying amarillo.gov as the official City of Amarillo website.

Estimated effort: Under 1 hour

What These Failures Mean Under DOJ Enforcement

The DOJ Title II Final Rule does not create a private right of action — it is enforced by DOJ through complaint investigation, voluntary compliance agreements, and, for egregious non-compliance, civil action. A resident who encounters a barrier can file a complaint with DOJ's Civil Rights Division or with the relevant federal funding agency. Most enforcement begins with a complaint, a notice of violation, and a voluntary resolution agreement requiring documented remediation and ongoing monitoring.

The failures we found on amarillo.gov are the kind that generate complaints. An unlabeled form input, a broken skip navigation link, social media icons with no accessible name — these are not obscure technical failures. They are barriers that a resident using JAWS, NVDA, or VoiceOver will encounter immediately on the first page visit. They are exactly what DOJ investigators look for when a complaint arrives.

The practical risk is not a fine — it is a consent decree requiring documented compliance within a timeline the city does not control, with external monitoring and periodic reporting obligations. That is a significantly worse outcome than a proactive audit and remediation plan initiated in the next 60 days.

A Practical Remediation Timeline for City of Amarillo

With April 26, 2027 as the hard deadline, here is a realistic 11-month window for a city of this size:

• Now through June 2026: Designate an internal compliance owner — typically the IT director, ADA coordinator, or both. Commission a professional WCAG 2.1 Level AA audit covering all public-facing web properties, not just the homepage. The failures we found on the homepage are a leading indicator; subsurface failures across forms, PDFs, and third-party embeds are virtually guaranteed.
• July–August 2026: Audit findings report delivered. Findings document each violation against its WCAG 2.1 success criterion with severity classification (critical, major, moderate). Remediation plan developed with assigned owners and target completion dates.
• September–November 2026: Remediation. Critical failures — keyboard traps, inaccessible authentication, unlabeled transactional forms — within 60 days. Major failures through October. Moderate findings through November.
• December 2026–January 2027: Re-audit of remediated findings. Verify fixes did not introduce new regressions. PDF library audit and video captioning verification if applicable.
• February–March 2027: DOJ-compliant accessibility statement published on amarillo.gov. Ongoing monitoring process established.
• April 26, 2027: Compliance deadline for City of Amarillo.

The failures we documented on the amarillo.gov homepage are fixable in hours, not weeks. The broader audit — covering all department pages, online forms, PDFs, and embedded third-party tools — is the work that requires a professional engagement and a structured remediation plan.

If you are the IT director, ADA coordinator, or web team lead for City of Amarillo and are beginning that process, we can help. Parallax is our fixed-fee WCAG 2.1 AA audit for government websites — findings report, remediation roadmap, and accessibility statement, delivered in 10 business days at $9,500 fixed fee. No hourly billing, no scope creep.

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