Morton Digital

2026-05-18 · 6 min read

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

Abstract editorial illustration: a government website accessibility compliance network for City of Olathe, Kansas, rendered in fine copper line work on dark slate, with WCAG accessibility markers at key compliance nodes. No text.

City of Olathe, Kansas — population 145,000+ [2] — operates olathe.org 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 olathe.org homepage directly from its live HTML to understand what accessibility barriers city residents currently face.

We found 2 verified Level A/A failures. 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 Olathe

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 145,000+, City of Olathe 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 olathe.org are representative of what we see across government websites of this size — fixable, documented, and addressable within the remaining timeline.

Verified WCAG Failures on olathe.org

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: Eight homepage images have no alt attribute — hero slides, navigation icons, UI elements (SC 1.1.1, Level A)

The olathe.org homepage contains eight img elements with no alt attribute — not an empty alt, entirely absent. Affected images include hero slider panels, department navigation icons, and UI elements. A missing alt attribute causes some screen readers to announce the raw file path — actively degrading the experience.

Fix: Add descriptive alt text to informational images; alt="" to purely decorative elements.

Estimated effort: 30–60 minutes

Finding 2: No skip navigation link — keyboard users must tab through full navigation on every page (SC 2.4.1, Level A)

The olathe.org homepage contains no skip navigation mechanism — no "Skip to Main Content" link, no ARIA landmark shortcut, no equivalent bypass. Every keyboard-only resident must tab through every navigation item, header element, and utility link before reaching page content, on every page visit.

Fix: Add a visually hidden "Skip to main content" anchor as the first focusable element, linking to an id="main-content" on the main element.

Estimated effort: 1–2 hours (one-time template change)

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 olathe.org 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 Olathe

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

The failures we documented on the olathe.org 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 Olathe 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.

Sources

  1. [1] Federal Register — Interim Final Rule extending Title II compliance dates (April 20, 2026) — "The compliance date for State and local government entities with a total population of 50,000 or more is extended from April 24, 2026, to April 26, 2027"
  2. [2] U.S. Census Bureau — QuickFacts: City of Olathe, Kansas — "Olathe city, Kansas — Population estimates, July 1, 2023: 144,891"
  3. [3] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "The rule covers web content and mobile apps that are provided by or on behalf of state and local governments."
  4. [4] WebAIM — The WebAIM Million (2024) — "In 2024, 95.9% of home pages had detectable WCAG 2 failures."

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