Morton Digital

2026-05-17 · 10 min read

Hennepin County Minnesota Government Website Accessibility: Minneapolis, Metro Transit, and the DOJ Title II Deadline

Abstract dark editorial illustration: a Hennepin County Minnesota compliance network rendered in fine copper line work on dark slate, with WCAG accessibility markers at Minneapolis city, Metro Transit, Hennepin Healthcare, and suburban city government nodes. No text.

# Hennepin County Minnesota Government Website Accessibility: What the DOJ Title II Rule Requires

Hennepin County is Minnesota's most populous county, home to approximately 1.28 million residents. Minneapolis — the state's largest city at approximately 425,000 — sits entirely within Hennepin County's borders, and seven additional cities above the 50,000-person threshold operate as independently covered entities under the same federal rule. Metro Transit, Hennepin Healthcare System, and a cluster of suburban cities (Brooklyn Park, Plymouth, Bloomington) each carry their own compliance obligations. The April 26, 2027 deadline is the controlling date for all of them.

Minnesota has an unusually strong disability rights advocacy infrastructure: Disability Rights Minnesota and the Governor's Council on Developmental Disabilities operate active monitoring programs, and the state's MNIT accessibility standard has made compliance language routine in state procurement. That context raises enforcement awareness across all Minnesota government entities — including Hennepin County's local governments.

---

Who Is Covered and Which Deadline Applies

April 26, 2027 (population ≥ 50,000)

Hennepin County. Hennepin County government has approximately 1.28 million residents — Minnesota's largest county — and faces the April 26, 2027 compliance deadline under the DOJ Title II Final Rule. [1] [2] The county's digital footprint includes the main county website, property tax search and payment systems, property and land survey portals, criminal justice systems (court records access, public safety data), public health and human services portals, recorder's office and vital records systems, and the Hennepin County Library digital infrastructure. [5]

City of Minneapolis. Minneapolis is Minnesota's largest city at approximately 425,000 residents and is independently covered under the DOJ Title II rule with an April 26, 2027 deadline. [4] The city's web compliance scope includes the main minneapolismn.gov portal, Minneapolis Police Department reporting tools, 311 service request systems, Minneapolis Regulatory Services licensing and permitting, Minneapolis Park and Recreation Board registration portals, the City Clerk's public records access system, election and voter registration tools, and all mobile applications the city distributes for resident use.

City of Bloomington. Bloomington, Minnesota has approximately 89,000 residents — independently covered with an April 26, 2027 deadline. The city's digital footprint includes permitting and development services, parks and recreation registration, public meeting records, and utility billing.

City of Brooklyn Park. Brooklyn Park has approximately 87,000 residents and faces the April 26, 2027 deadline. Brooklyn Park is one of the most ethnically diverse cities in Minnesota — a factor that makes accessible digital services particularly important for reaching all residents through government portals.

City of Plymouth. Plymouth has approximately 82,000 residents and faces the April 26, 2027 deadline. The city's government website covers development and permitting, parks programs, public safety, and utility access.

Metro Transit. Metro Transit operates the METRO light rail network (Blue, Green, Orange, and A Lines), the Northstar commuter rail line, and extensive bus service across the seven-county Twin Cities metropolitan area. It is an independent public entity with its own April 26, 2027 compliance deadline. [6] Metro Transit's compliance scope covers its main website, trip planning tools, real-time transit tracking, mobile app, rider alerts, paratransit and Metro Mobility services, station information pages, schedule PDFs, and all digital rider-facing services.

Hennepin Healthcare System. Hennepin Healthcare operates Hennepin County Medical Center (HCMC), a public Level 1 trauma center and the largest safety-net hospital in Minnesota. As a public entity, Hennepin Healthcare's website and digital patient-facing tools are covered by the DOJ Title II rule, with an April 26, 2027 deadline. [7] Patient portal accessibility, appointment scheduling, public health information, and hospital navigation tools are all in scope.

April 26, 2028 (population < 50,000)

Minneapolis Public Schools (MPS). MPS serves approximately 28,000 enrolled students — below the 50,000 threshold — placing it in the April 26, 2028 compliance tier. [10] MPS's digital scope includes the district website, school-level pages, parent and student portals, online enrollment systems, special education documentation, school meal applications, board meeting records, and published PDFs. Minneapolis has one of the most linguistically diverse student populations in the Midwest — accessible parent portals directly affect service equity.

Minneapolis Community and Technical College (MCTC). MCTC serves approximately 12,000 students — below the 50,000 threshold — and has until April 26, 2028 to achieve WCAG 2.1 Level AA conformance.

Metropolitan State University. Metropolitan State serves approximately 10,000 students — below the 50,000 threshold — and faces the April 26, 2028 deadline as a public institution.

---

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. [5] For Hennepin County entities, that includes:

The compliance obligation stays with the government entity. A vendor's accessibility statement does not satisfy the government's obligation. Every technology contract renewed or signed after your compliance date should require WCAG 2.1 AA conformance as a mandatory deliverable, with testing documentation.

---

What WCAG 2.1 Level AA Requires

WCAG 2.1 Level AA has 50 success criteria organized under four principles. [8]

Perceivable — content must be available to all senses. Informational images require descriptive alt text. All prerecorded video with audio requires captions. Color contrast must meet 4.5:1 for normal text and 3:1 for large text and UI components. Content must reflow to a single column at 320px without horizontal scrolling. Information cannot be conveyed by color alone.

Operable — all functionality must work without a mouse. Keyboard navigation must reach every interactive element without creating focus traps. Skip navigation links must allow users to bypass repetitive page headers. Focus indicators must be visible at all times. Time limits in forms and sessions must be user-controllable.

Understandable — page language must be declared in HTML. Forms must have visible labels, clear error identification in text (not just color), and correction suggestions when format errors occur. Navigation patterns must remain consistent across pages.

Robust — HTML must be valid, with correct ARIA roles and attribute values so that screen readers and other assistive technology can accurately parse and interact with the interface.

The WebAIM Million 2024 report found that 95.9% of home pages had detectable WCAG 2 failures, with the five most common failures being low contrast text (81.0%), missing alt text (54.5%), missing form input labels (48.6%), empty links (44.6%), and missing document language (17.1%). [9] Government sites follow this same pattern — and complex portals for property tax, transit, human services, and health systems typically add additional failures that automated scanners cannot detect.

---

The Most Common Failure Categories for Hennepin County Government Sites

1. Property tax and land records portals. Hennepin County's property tax search, payment, and records systems are among the highest-traffic county digital services. These portals are typically database-driven with dynamically generated content — tables of parcel records, assessment notices, and tax statement PDFs. Common WCAG failures include data tables without proper header markup (WCAG 1.3.1), missing focus management when results load dynamically (WCAG 2.4.3), and property-related PDF documents without accessible tag structure.

2. Metro Transit's real-time services. Metro Transit's trip planner, real-time arrival boards, and mobile app are among the most accessibility-critical services in the region — transit riders who are blind or have low vision depend on them for independent travel. Real-time transit applications are structurally prone to accessibility failures: they load dynamic content via JavaScript, use timed refresh cycles that disrupt screen reader announcements (WCAG 4.1.3), and frequently embed third-party map widgets that lack keyboard accessibility (WCAG 2.1.1). These failures require manual testing with NVDA on Windows and VoiceOver on iOS — automated scanners cannot detect them.

3. Human services and public health portals. Hennepin County's Department of Human Services operates digital systems for benefits enrollment, case management, and social services access. These systems serve populations — low-income residents, people with disabilities, older adults — who are disproportionately likely to need accessible digital interfaces. Common failures: inaccessible multi-step forms (missing labels at WCAG 1.3.1, inadequate error identification at WCAG 3.3.1), PDF-based application forms scanned as images without text layers, and content requiring specific reading order that is not structurally encoded.

4. Minneapolis permitting and licensing systems. Minneapolis Regulatory Services handles high-volume licensing for business, construction, and code compliance. Multi-step online permit applications frequently fail: custom form controls without ARIA labels (WCAG 4.1.2), session timeouts that do not warn the user (WCAG 2.2.1), focus management that breaks when navigating between form sections (WCAG 2.4.3), and error messages that identify the error by color alone without text identification (WCAG 3.3.1).

5. PDF accessibility across all Hennepin entities. Every Hennepin County entity — the county, city of Minneapolis, suburban cities, school district, transit authority — publishes large volumes of PDFs: budget documents, ordinances, board meeting minutes, transit schedules, environmental review notices, health plan documents. Many exist as scanned image files or digitally created PDFs without accessible tag structure, reading order, or alt text for charts and diagrams. Government PDFs are explicitly in scope when they provide access to services, programs, or activities.

6. Hennepin Healthcare patient portal and public health information. Hennepin Healthcare's patient portal, appointment systems, and public health resources are covered by Title II as a public entity's digital services. Healthcare portals share the same common failure patterns as other complex portals — missing form labels, inaccessible date pickers, error messages that rely on color — with the added urgency that users may be managing serious health conditions when they need to access these systems.

---

Compliance Timeline for Hennepin County Entities

The April 26, 2027 deadline for Hennepin County, Minneapolis, Bloomington, Brooklyn Park, Plymouth, Metro Transit, and Hennepin Healthcare is roughly 11 months from now. A realistic compliance program:

Minneapolis Public Schools (April 2028), MCTC (April 2028), and Metropolitan State (April 2028) have the additional year but should begin planning in 2025 rather than 2027 to avoid timeline compression on complex portals.

---

Enforcement Context

The DOJ enforces Title II through complaint investigation. When voluntary compliance cannot be achieved, DOJ can pursue formal consent decrees, binding remediation plans, and court monitoring. Minnesota's active disability advocacy organizations — Disability Rights Minnesota and the Governor's Council on Developmental Disabilities — have established channels for filing federal complaints and coordinating with advocacy networks nationally. [11] [12] Enforcement awareness in Minnesota is above the Midwestern average precisely because these organizations are active and institutionally resourced.

A documented compliance program — where the entity can show it scoped the problem, conducted an audit, produced a remediation plan, and is executing against it — is treated materially differently by DOJ than entities with no documented compliance effort when a complaint arrives.

---

Regional and State Context

The DOJ Title II rule applies uniformly across state lines:

Sources

  1. [1] Federal Register — 28 CFR Part 35: Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (April 24, 2024) — "This final rule amends the Department of Justice's regulation implementing title II of the Americans with Disabilities Act (ADA) by adding specific technical requirements for web accessibility."
  2. [2] 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"
  3. [3] U.S. Census Bureau — QuickFacts Hennepin County, Minnesota — "Hennepin County, Minnesota — Population estimates, July 1, 2023: 1,281,565"
  4. [4] U.S. Census Bureau — QuickFacts Minneapolis city, Minnesota — "Minneapolis city, Minnesota — Population estimates, July 1, 2023: 425,336"
  5. [5] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "State and local governments must make sure that their web content and mobile apps meet WCAG 2.1, Level AA"
  6. [6] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "Transit authorities are state and local government entities covered by Title II of the ADA and must comply with the web accessibility rule."
  7. [7] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "The rule covers web content and mobile apps that public entities make available to the public or use to offer their services, programs, or activities."
  8. [8] W3C Web Accessibility Initiative — WCAG 2.1 Specification — "Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible."
  9. [9] WebAIM — The WebAIM Million: An Annual Accessibility Analysis of the Top 1,000,000 Home Pages (2024) — "In 2024, 95.9% of home pages had detectable WCAG 2 failures. The most common failures were low contrast text (81.0%), missing alternative text (54.5%), missing form labels (48.6%), empty links (44.6%), and missing document language (17.1%)."
  10. [10] ADA.gov — DOJ Title II Web Accessibility Final Rule Compliance Dates — "Title II entities with a total population of fewer than 50,000: 4 years after the date of publication of the final rule (April 26, 2028)."
  11. [11] Minnesota IT Services (MNIT) — Accessibility — "MNIT promotes digital accessibility across state government to ensure all Minnesotans can access state services online."
  12. [12] Minnesota Governor's Council on Developmental Disabilities — official website — "The Minnesota Governor's Council on Developmental Disabilities advances the self-determination, independence, productivity, and integration of people with developmental disabilities in Minnesota communities."

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