2026-05-17 · 9 min read

Minnesota Government Website Accessibility: What the DOJ Title II Rule Means for Your Agency

# Minnesota Government Website Accessibility: What the DOJ Title II Rule Means for Your Agency

Minnesota has 87 counties. Add the state's hundreds of municipalities, townships, independent school districts, transit authorities, public universities, and special districts, and Minnesota has one of the most geographically distributed local government landscapes in the Midwest. The DOJ Title II Final Rule applies to every one of those entities that meets the population threshold — and the largest ones face a deadline less than a year away.

If you are a Minnesota government IT director, ADA coordinator, or compliance officer, this post gives you the specific compliance requirements, who is covered, what is covered, how Minnesota IT Services (MNIT) interacts with the federal rule, and the compliance picture across Minnesota's major metro areas and counties.

Who Is Covered

The federal rule applies to state and local government entities with a total population of 50,000 or more. The April 26, 2027 deadline applies to those jurisdictions. Entities under 50,000 have until April 26, 2028 — the standard is identical; only the timeline differs. ^[1]

In Minnesota, that covers:

Minnesota state government — the state of Minnesota and all executive branch agencies are covered. That includes the Minnesota Department of Transportation (MnDOT), the Minnesota Department of Education (MDE), the Minnesota court system, the Minnesota Department of Human Services, and dozens of other agencies, each with their own web properties. Minnesota IT Services (MNIT) manages centralized IT and accessibility standards for state agencies. ^[5]

Major Minnesota counties — Hennepin County (~1.28 million), Ramsey County (~560,000), Dakota County (~420,000), Anoka County (~370,000), Washington County (~270,000), St. Louis County (~200,000), Olmsted County (~165,000), Scott County (~160,000), and Carver County (~110,000) are all well above the 50,000 threshold and face the April 26, 2027 deadline. ^{[4] [7] [11]}

Major Minnesota cities — Minneapolis (~425,000), Saint Paul (~310,000), Rochester (~125,000), Duluth (~90,000), Brooklyn Park (~87,000), Bloomington (~89,000), Plymouth (~82,000), Maple Grove (~74,000), Woodbury (~76,000), and St. Cloud (~68,000) are all above 50,000 and are independently covered entities.

Transit authorities — Metro Transit, which serves the seven-county Twin Cities metropolitan area with METRO light rail (Blue, Green, Orange, and A Lines), Northstar commuter rail, and extensive bus service, is an independently covered entity. Each transit authority faces its own April 26, 2027 deadline for websites, trip planners, real-time apps, and schedule documents. ^[8]

Public universities and community colleges — the University of Minnesota (~52,000 students), Minnesota State University Mankato (~14,000), and other public institutions with populations above 50,000 are independently covered entities with April 2027 deadlines. Institutions below the 50,000 threshold have until April 2028.

Public school districts — Minnesota has approximately 330 public school districts. Districts with enrollment above 50,000 face April 2027; smaller districts have until April 2028. Minneapolis Public Schools (~28,000 enrolled students) falls in the April 2028 tier.

Hennepin Healthcare System — Hennepin County Medical Center (HCMC), a public Level 1 trauma center and the largest safety-net hospital in Minnesota, is a public entity with web compliance obligations under the April 26, 2027 deadline. ^[8]

Libraries, public utilities, and special districts — the Hennepin County Library system, the Saint Paul Public Library, and other independent public entities must each assess their own threshold position.

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. ^[8] For Minnesota government entities, that includes:

• The main public website and all subdomains
• Web-based applications residents use: permit portals, property tax systems, licensing applications, benefits portals, court case lookup tools
• Mobile apps distributed to the public
• Documents published through any of the above: PDFs, Word files, spreadsheets, presentations, court forms

Third-party content procured or controlled by the agency is in scope. If you contracted a vendor to build your permitting system, that system must meet WCAG 2.1 AA. The compliance responsibility transfers to you as the contracting entity. Every technology contract signed after your compliance date should include WCAG 2.1 AA conformance as a mandatory deliverable.

---

Minnesota's State Accessibility Framework: MNIT

Minnesota adds a state-level compliance layer through Minnesota IT Services (MNIT). MNIT is the central state agency responsible for IT policy for Minnesota executive branch agencies and publishes an accessibility standard requiring conformance to WCAG 2.1 Level AA. ^[5] MNIT's role encompasses procurement policy, vendor management, and technical standards for state agency digital properties.

For Minnesota state agencies, this means two compliance frameworks run in parallel: the MNIT state standard and the DOJ Title II Final Rule. The substantive target — WCAG 2.1 Level AA — is the same under both. The enforcement mechanisms are distinct: the state framework is enforced through MNIT administrative channels; the federal rule is enforced through DOJ complaint investigations and, ultimately, federal court.

Minnesota's MNIT accessibility framework means that state agencies have had institutional exposure to WCAG 2.1 AA requirements and should have a baseline policy infrastructure in place. That institutional history does not guarantee compliance — agencies with legacy systems, Minnesota courts, and state-affiliated entities may have uneven conformance — but it creates policy awareness that is absent in many other states.

Local governments in Minnesota — counties, cities, townships, transit authorities, school districts — are primarily subject to the federal DOJ rule rather than the MNIT state standard. The technical requirement is identical: WCAG 2.1 Level AA.

---

Minnesota's Disability Rights Infrastructure

Minnesota has strong disability rights advocacy through the Governor's Council on Developmental Disabilities and Disability Rights Minnesota. ^[12] These organizations monitor government digital services and support individuals filing ADA Title II complaints. Minnesota's disability rights community is active and organized — enforcement awareness and complaint capacity are above average compared to most other Midwestern states.

This matters for government IT directors because the enforcement mechanism under the DOJ Title II rule begins with complaints. An active disability rights advocacy community means complaints are more likely to be filed, more likely to reach the DOJ, and more likely to result in formal investigation. The April 2027 deadline is not theoretical.

---

What WCAG 2.1 Level AA Requires

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

Perceivable — content must be presentable in ways users can perceive. Alt text for informational images. Captions for prerecorded video. Transcripts for audio. Sufficient color contrast: 4.5:1 for normal text, 3:1 for large text. Content that reflows to a single column at 320px without horizontal scrolling.

Operable — all functionality must work without a mouse. Keyboard navigation must reach every interactive element. No time limits that trap users. No content that flashes more than three times per second. Skip navigation links that allow users to bypass repeated header elements.

Understandable — the language of the page must be declared in HTML so screen readers pronounce content correctly. Forms must include visible labels, error messages that identify what is wrong, and suggestions for how to fix it. Navigation must be consistent across pages.

Robust — HTML must be valid, with proper ARIA roles and attributes so assistive technology can parse and interact with the interface.

The WebAIM Million 2024 report found that 95.9% of home pages had detectable WCAG 2 failures. ^[10] The five most common: low contrast text (81%), missing alt text (54.5%), missing form labels (48.6%), empty links (44.6%), and missing document language (17.1%). Minnesota government sites follow the same failure patterns seen nationally.

---

The Three Most Common Failure Categories for Minnesota Government Sites

1. PDF accessibility. Minnesota government entities publish extensive volumes of PDFs — budget documents, ordinances, meeting minutes, permit applications, court forms, road plans, and regulatory guidance. Most of these are inaccessible. Scanned-image PDFs — common for older records — are unreadable by screen readers. Even digitally created PDFs typically lack the tag structure, reading order, and accessible form fields that WCAG requires. The rule covers PDFs when they provide access to government services, programs, and activities. ^[8]

2. Accessible forms for government services. Minnesota permit portals, property tax payment systems, licensing applications, benefits portals, and registration systems commonly fail WCAG 1.3.1 (form fields lack programmatically associated labels), 3.3.1 (errors not identified in text), and 3.3.3 (no suggestions provided for correcting errors). When a resident cannot complete a permit application or access a benefit because the form is inaccessible, it is a service failure with legal consequences.

3. Keyboard inaccessibility in complex interactions. Custom navigation menus, interactive GIS maps, property search tools, date pickers, and modal dialogs — common in Minnesota county permit portals, court systems, and transit applications — frequently trap keyboard users or become unreachable without a mouse. WCAG 2.1.1 (Keyboard), 2.1.2 (No Keyboard Trap), and 2.4.7 (Focus Visible) are among the most common failures that automated scanners cannot detect.

---

Compliance Timeline for Minnesota Entities

Minnesota covered entities have until April 26, 2027. A realistic WCAG compliance program for a mid-size Minnesota government entity:

• Weeks 1–4: Scope the digital footprint — inventory all web properties, subdomains, mobile apps, and document repositories.
• Weeks 5–12: Commission an audit covering automated scanning, manual testing with assistive technology (NVDA, JAWS, VoiceOver), and document review.
• Weeks 13–24: Remediation planning — prioritize findings by severity and service impact, assign ownership, set milestones.
• Weeks 25–40: Remediation — developers fix code, document teams reformat PDFs, procurement adds WCAG requirements to new vendor contracts.
• Weeks 41–48: Validation testing — re-test against WCAG 2.1 AA to confirm remediation is complete.
• Weeks 49–52: Publish an accessibility statement, establish ongoing monitoring, train staff.

Entities that begin now have a realistic path to April 2027 compliance. Entities that delay past fall 2026 will not.

---

Minnesota's Major Metro and County Compliance Profiles

Hennepin County / Minneapolis. Minnesota's most populous county (~1.28 million) and largest city (~425,000). Hennepin County government, the City of Minneapolis, Metro Transit, Hennepin Healthcare, and the cities of Brooklyn Park (~87,000), Bloomington (~89,000), and Plymouth (~82,000) all face the April 26, 2027 deadline as independently covered entities. Minneapolis has an active disability rights community and a large assistive technology user base. See the detailed Hennepin County compliance guide.

Ramsey County / Saint Paul. Minnesota's second most populous county (~560,000) and the state capital city. Ramsey County government and the City of Saint Paul are independently covered entities with April 2027 deadlines. State agency presence in Saint Paul creates concentrated enforcement awareness. See the Ramsey County compliance guide.

Dakota County. Dakota County (~420,000), home to Apple Valley, Eagan, and Burnsville, is a well-populated Twin Cities suburban county with an April 2027 deadline. Dakota County's government portal and county-contracted digital services are in scope.

Anoka County. Anoka County (~370,000) serves a broad northern Twin Cities suburban corridor. The county government and all municipalities above 50,000 face April 2027 deadlines as independently covered entities.

Washington County. Washington County (~270,000), home to Woodbury and Stillwater, faces the April 2027 deadline. Rapid suburban growth means digital services designed for a smaller population are now serving a much larger one.

St. Louis County / Duluth. St. Louis County (~200,000) and the City of Duluth (~90,000) are independently covered entities with April 2027 deadlines. The county covers one of the largest geographic areas in Minnesota — a large digital footprint relative to population density.

Olmsted County / Rochester. Olmsted County (~165,000) and the City of Rochester (~125,000) — home to the Mayo Clinic — face the April 2027 deadline. The Mayo Clinic's large disabled and medically complex patient population creates an unusually high demand for accessible government digital services in the Rochester area.

Scott County. Scott County (~160,000) and Carver County (~110,000) are growing Twin Cities southwestern suburbs with April 2027 deadlines.

---

Minnesota County-Level Compliance Guides

Detailed compliance guidance for Minnesota's most populous county:

• Hennepin County Minnesota government website accessibility — Hennepin County government, City of Minneapolis, Metro Transit, Hennepin Healthcare, Brooklyn Park, Plymouth, Bloomington, and Minneapolis Community and Technical College

For comparison with Minnesota's compliance picture, see:

• Ohio government website accessibility — 88 counties and the full Title II compliance picture for a neighboring Great Lakes state
• Michigan government website accessibility — 83 counties and the Michigan DTMB parallel state standard
• Government website ADA compliance 2027 — the complete guide to the federal rule and April 2027 deadline

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 →