ADA Laws in Minnesota

ADA laws in Minnesota: what they require for websites, businesses, and public agencies

ADA laws in Minnesota are federal first, state second. Website accessibility in Minnesota is driven by the Americans with Disabilities Act of 1990 and enforced through federal courts, with additional state-level protections under the Minnesota Human Rights Act (MHRA), Minn. Stat. § 363A.01 et seq.

There is no standalone “Minnesota website accessibility statute” that lays out technical coding rules. But businesses in Minneapolis, St. Paul, Rochester, Duluth, Bloomington, and across the state are being evaluated under federal ADA standards when their websites block access to goods and services. Public agencies in Minnesota are now under a binding federal regulation that names a specific technical standard: WCAG 2.1 Level AA.

That is where the compliance work actually happens. In code. Not in press releases.

This article breaks down how ADA laws in Minnesota apply to websites, how courts in the Eighth Circuit treat digital access claims, how the Minnesota Human Rights Act fits into the picture, what the 2024 Department of Justice rule means for state and local agencies, what litigation looks like in practice, and what compliance actually costs.

No gloss. Just structure.

The federal framework controlling ADA website compliance in Minnesota

The Americans with Disabilities Act was signed into law on July 26, 1990. It prohibits disability discrimination in employment (Title I), state and local government services (Title II), and places of public accommodation (Title III).

For websites in Minnesota, two titles matter:

Title II applies to state and local government entities.
Title III applies to private businesses that qualify as places of public accommodation.

Websites are not mentioned explicitly in the 1990 statute. The courts extended ADA coverage to digital services as websites became the primary way businesses and governments interact with the public.

Minnesota is in the Eighth Circuit. Federal ADA website cases filed in Minnesota are heard in the U.S. District Court for the District of Minnesota, with appeals going to the Eighth Circuit Court of Appeals.

The Eighth Circuit has not issued a sweeping decision declaring that all websites are public accommodations by themselves. Instead, district courts in Minnesota have generally evaluated whether the website has a sufficient connection, often called a “nexus,” to a physical place of public accommodation.

That means:

If a business in Minnesota operates a brick-and-mortar location open to the public and its website is tied to that location, the ADA likely applies to the website.

Purely online businesses without a physical location face a more unsettled legal environment in this circuit. But plaintiffs still file cases. And many defendants settle rather than litigate the threshold issue.

There is no safe category of “small enough to ignore it.” Title III does not include a revenue exemption.

The Minnesota Human Rights Act and disability discrimination

Minnesota has its own civil rights statute, the Minnesota Human Rights Act (MHRA). It prohibits discrimination in employment, housing, education, and public accommodations based on disability and other protected characteristics.

The MHRA predates many modern ADA website cases and does not contain detailed technical standards for digital accessibility. Most website accessibility claims in Minnesota are brought under federal ADA Title III, often with state law claims added as supplemental counts.

The Minnesota Department of Human Rights enforces the MHRA. Employment-related digital accessibility issues may proceed through administrative channels before litigation. Public accommodation website cases usually proceed directly in federal court under the ADA.

The practical result is this: federal ADA doctrine drives the technical compliance standard for Minnesota websites. The MHRA reinforces the general prohibition against disability discrimination but does not create a separate WCAG-like framework.

The 2024 DOJ Title II rule and Minnesota government websites

On April 24, 2024, the U.S. Department of Justice issued a final rule updating Title II regulations under the ADA. For the first time, the federal government adopted a specific technical standard for web and mobile accessibility in binding regulations.

The rule requires state and local government entities to make their websites and mobile apps conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

That applies in Minnesota to:

• State of Minnesota agencies
• Counties such as Hennepin, Ramsey, and Dakota
• Cities including Minneapolis and St. Paul
• Townships
• Public school districts
• Public colleges and universities, including the University of Minnesota system and Minnesota State Colleges and Universities

The compliance deadlines depend on population size. Larger public entities generally have two years from publication of the rule. Smaller entities have three years.

This is not advisory guidance. It is federal regulation.

If a Minnesota county website allows residents to pay property taxes online, apply for permits, or access court forms, that site must conform to WCAG 2.1 AA by the applicable deadline.

There are limited exceptions for archived content and certain third-party content not controlled by the agency. But the baseline is conformance.

There is a budget trade-off here. Some rural Minnesota counties operate with limited IT staff and legacy content management systems built more than a decade ago. Retrofitting thousands of PDF documents to be screen reader accessible can require substantial staff time or outside vendor contracts.

The rule does not contain a general budget hardship exemption. It does allow limited flexibility in cases of fundamental alteration or undue financial and administrative burden, but those defenses are narrow and must be documented.

What WCAG 2.1 AA requires in practical terms

WCAG 2.1 AA is a technical standard developed by the World Wide Web Consortium (W3C). It is structured around four principles: perceivable, operable, understandable, and robust.

Those categories translate into specific coding requirements.

Common issues in Minnesota ADA website cases include:

Missing alternative text for images
Low color contrast between text and background
Navigation menus that cannot be accessed by keyboard
Forms without properly associated labels
Error messages that are not announced to screen readers
PDF documents that are not tagged for accessibility

Color contrast requirements are measurable. Normal text must have a contrast ratio of at least 4.5:1 against its background. Larger text has a lower threshold.

Keyboard accessibility means that a user who cannot use a mouse must be able to navigate every interactive element using only the keyboard. If a drop-down menu opens only on mouse hover and cannot be triggered by keyboard focus, that is a failure.

Automated testing tools can detect some of these problems. They cannot detect all of them. Manual testing with screen readers such as NVDA or JAWS on Windows and VoiceOver on macOS and iOS is necessary to evaluate real-world usability.

WCAG compliance is not a binary switch. It is a structured engineering effort.

ADA website lawsuits in Minnesota: how they typically unfold

ADA website lawsuits in Minnesota usually begin with a demand letter.

The letter often identifies a plaintiff who uses a screen reader and alleges that the website contains barriers that prevent access to goods and services. The letter may include screenshots and citations to specific WCAG success criteria.

If the matter does not resolve quickly, a complaint is filed in the U.S. District Court for the District of Minnesota.

The complaint typically alleges:

• The defendant operates a place of public accommodation in Minnesota.
• The defendant’s website is connected to that physical location.
• The website contains accessibility barriers.
• The plaintiff was denied equal access.
• The defendant is in violation of Title III of the ADA.

Under Title III, private plaintiffs generally seek injunctive relief and attorney’s fees. They do not receive compensatory damages under the federal statute.

That shapes the economics of the case.

Attorney’s fees in Minnesota ADA website settlements often range from $10,000 to $35,000 depending on how far the case proceeds. If the defendant files motions and litigates aggressively, fees can increase.

Remediation costs are separate.

A mid-size ecommerce retailer in the Twin Cities might spend $15,000 to $40,000 on remediation after an audit. Combined with attorney’s fees, total out-of-pocket costs can exceed $50,000.

Most cases settle before trial.

A real-world example from the Twin Cities

In 2022, a Minneapolis-based specialty retail store received a demand letter alleging that its online store was not accessible to screen reader users.

The site was built on a custom theme with heavy JavaScript for product filtering. The plaintiff’s counsel identified the following issues:

• Product images without alt text
• Filter controls that were not keyboard operable
• Error messages on the checkout page that were not announced to screen readers
• Low contrast promotional banners

The business initially believed that its third-party ecommerce platform was responsible for accessibility. The demand letter cited case law indicating that a business cannot avoid ADA liability by outsourcing website development.

The store hired an accessibility consultant to perform a WCAG 2.1 AA audit. The audit report identified 68 distinct failures across templates.

Remediation cost approximately $24,000 over four months. The settlement required payment of $18,500 in attorney’s fees and a commitment to bring the site into WCAG 2.1 AA conformance within 12 months.

The owner later admitted that the redesign improved mobile usability overall. But the process required freezing marketing updates during remediation.

Time was the hidden cost.

The nexus requirement in the Eighth Circuit

Unlike some circuits that have taken broader views, courts in the Eighth Circuit have generally required a connection between the website and a physical place of public accommodation.

If a Minnesota business operates a restaurant in St. Paul and uses its website for reservations and online ordering, the nexus is clear.

If a business operates entirely online without a physical location open to the public, the analysis becomes more complicated. District courts in Minnesota have not uniformly extended Title III to purely digital businesses without physical storefronts.

This creates uncertainty for digital-only companies headquartered in Minnesota. Some may argue lack of nexus. Others choose to remediate rather than test the boundaries.

Uncertainty is not immunity.

Employment-related website accessibility in Minnesota

Title I of the ADA applies to employers with 15 or more employees. It covers discrimination in hiring and employment practices.

In Minnesota, this affects:

• Online job applications
• Applicant tracking systems
• Employee portals

If a visually impaired applicant cannot complete an online job application because the form fields are unlabeled or time out too quickly, that may constitute a Title I violation.

Complaints often begin with the Equal Employment Opportunity Commission. The Minnesota Department of Human Rights may also receive related complaints under the MHRA.

Employment-related accessibility issues are less publicly visible than retail website lawsuits. They still carry legal exposure.

Higher education and digital accessibility in Minnesota

Public colleges and universities in Minnesota fall under Title II and must comply with the DOJ’s 2024 WCAG 2.1 AA rule.

That includes:

• Admissions portals
• Course registration systems
• Financial aid applications
• Learning management systems
• Online course materials

Section 504 of the Rehabilitation Act of 1973 also applies to institutions receiving federal funding. Many Minnesota public universities receive substantial federal funds.

Digital accessibility in higher education extends beyond marketing pages. It includes captioned lecture videos, accessible PDFs, properly structured HTML course content, and compatible exam platforms.

Remediation at this scale is expensive. Large universities often maintain dedicated accessibility offices with staff responsible for auditing and training faculty.

Smaller institutions face tighter resource constraints.

Accessibility overlays and their limits in Minnesota

Some Minnesota businesses install accessibility overlay tools after receiving a demand letter. These tools typically add a toolbar that allows users to adjust text size, contrast, or other visual settings.

Overlays do not correct underlying HTML structure. They do not automatically add meaningful alt text to images. They do not rebuild inaccessible JavaScript widgets.

Courts in various jurisdictions have rejected arguments that overlays alone moot ADA claims if structural barriers remain. There is no safe harbor provision in the ADA for installing a widget.

Overlays are inexpensive compared to full remediation. Annual costs may be under $1,000.

They have not stopped litigation.

Cost of ADA website compliance in Minnesota

Costs depend on site size and complexity.

Small informational site (10–25 pages):
Audit: $2,000–$6,000
Remediation: $4,000–$12,000

Mid-size ecommerce site (500–2,000 products):
Audit: $6,000–$15,000
Remediation: $15,000–$50,000

Large enterprise or government portal:
Audit: $20,000+
Remediation: often six figures

These figures reflect 2024–2025 pricing from accessibility consultants operating in the Midwest.

Litigation costs often exceed proactive compliance costs, especially if the case proceeds beyond initial motions.

There is no official ADA certification body. Vendors offering “ADA certified” badges are not issuing government-backed credentials.

Compliance is documented through audits, remediation reports, and ongoing testing.

Standing and mootness arguments in Minnesota ADA cases

Defendants sometimes challenge whether the plaintiff has standing to sue, arguing that the plaintiff does not intend to return to the website or physical location.

Minnesota federal courts analyze standing under Article III of the U.S. Constitution. Plaintiffs typically allege intent to return once barriers are removed.

Mootness arguments arise when defendants remediate the website after the lawsuit is filed. To succeed on mootness, a defendant must show that the alleged violations are fully corrected and unlikely to recur.

Partial remediation is rarely sufficient. Courts require evidence.

These defenses are fact-specific and not guaranteed.

Ongoing compliance: not a one-time fix

One limitation of WCAG-based compliance is that websites are dynamic.

Marketing teams upload new images. Developers add new features. Third-party plugins update automatically.

A site that passed a WCAG 2.1 AA audit in January can fail in June after design changes.

Sustainable compliance requires:

• Documented accessibility policy
• Periodic audits
• Manual keyboard and screen reader testing
• Content guidelines for staff

Without internal processes, accessibility degrades.

ADA laws in Minnesota: bottom line

ADA laws in Minnesota apply to websites connected to physical places of public accommodation under Title III and to state and local government websites under Title II. As of April 24, 2024, public entities must comply with WCAG 2.1 Level AA under federal regulation. The Minnesota Human Rights Act reinforces disability discrimination protections but does not set a separate digital standard.

Website accessibility litigation in Minnesota proceeds primarily in federal court. Private plaintiffs typically seek injunctive relief and attorney’s fees. Remediation costs vary by site complexity but often fall below the combined cost of defense and settlement.

Compliance is technical and ongoing. There is no state-specific digital statute replacing federal law. The controlling standards are federal ADA doctrine and, for public entities, the DOJ’s WCAG 2.1 AA rule. Businesses and agencies operating in Minnesota are evaluated under that structure whether they planned for it or not.