Responsive ADA Mobile Websites

After years of lawsuits and confusion, the DOJ did something concrete. On April 24, 2024, they published a final rule adopting WCAG 2.1 Level AA as the technical standard for state and local government websites and mobile apps .

This isn't guidance anymore. It's regulation. It's published in the Federal Register and codified in 28 CFR Part 35 Subpart H .

The rule applies to all web content and mobile apps that public entities "provide or make available, directly or through contractual, licensing, or other arrangements" . That last part matters. If you hire a vendor to build your site or app, you're still responsible for making sure it's accessible. The DOJ's compliance guide explicitly says towns need to make sure web developers understand these requirements .

The deadlines are real

The compliance dates depend on population size, and they're coming fast .

For public entities with 50,000 or more people, compliance is required by April 24, 2026. That includes state governments, large counties and cities, and state universities regardless of their student population .

For entities with populations under 50,000, and for special district governments like transit authorities or water districts, the deadline is April 26, 2027 .

The DOJ's guidance makes clear how to calculate population. A city police department uses the city's population. A county library uses the county's population. A state university uses the state's population, not its student count .

What responsive actually means for accessibility

Here's where responsive design intersects with WCAG.

Responsive sites use CSS media queries to adapt layout based on screen width. That's fine. But WCAG 2.1 includes specific success criteria that become critical on mobile .

1.3.4 Orientation (Level AA) : Content isn't locked to portrait or landscape unless a specific display orientation is essential. That video player that only works in landscape? Violation. The app that forces portrait mode? Violation .

1.3.5 Identify Input Purpose (Level AA) : Form fields that collect user information must have programmatically identifiable purposes. When your mobile checkout asks for name, email, and address, browsers should auto-fill correctly. This requires proper autocomplete attributes .

1.4.10 Reflow (Level AA) : Content must display without losing information or requiring two-dimensional scrolling at 400 percent zoom. On mobile, this means users who increase text size shouldn't have to scroll horizontally to read sentences .

1.4.12 Text Spacing (Level AA) : Users must be able to override text spacing without losing content. If someone needs more line height or wider letter spacing, your responsive design shouldn't break .

2.5.1 Pointer Gestures (Level A) : All functionality that uses multipoint or path-based gestures must also be operable with single-point activation. Swipe to delete? Also need a button. Pinch to zoom? Also need controls .

2.5.2 Pointer Cancellation (Level A) : Don't execute functions on mouse-down or touch-start. Give users the ability to cancel by moving their finger away. This prevents accidental purchases .

2.5.4 Motion Actuation (Level A) : Functions triggered by device motion (shake, tilt) must also be operable with UI controls. If your app only responds to shaking, it fails .

2.5.8 Target Size (Minimum) (Level AA, WCAG 2.2) : Touch targets must be at least 24 by 24 pixels, with exceptions for inline links and essential controls. Those tiny close buttons in the corner of modals? They need to be big enough to hit without zooming .

The mobile app problem

Mobile apps are explicitly covered. The rule defines "mobile app" as software applications downloaded and designed to run on mobile devices .

This means native iOS and Android apps need to meet WCAG 2.1 AA just like websites. The technical implementation differs, but the success criteria are the same.

The Husqvarna class action settlement from December 2025 shows how seriously courts take this. Husqvarna agreed to make its website and any new website or mobile app it develops accessible to individuals who are blind or visually disabled . That's a legally binding commitment covering future development.

What's exempt

The rule includes specific exceptions .

Archived web content is exempt if it was created before the compliance date, is kept only for reference or recordkeeping, isn't updated after archiving, and lives in a clearly identified archived area . The DOJ warns that governments can't just label everything "archived" to avoid compliance. The exception is narrow.

Preexisting conventional electronic documents like PDFs, Word files, and spreadsheets are exempt unless they're currently used to apply for, access, or participate in services . Old water quality reports from 2010? Probably exempt. The current benefit application form? Must be accessible.

Third-party content is exempt unless the third party is posting under contract with the government . Social media posts from before the compliance date are exempt. Password-protected documents about specific individuals are exempt .

The equivalent facilitation option

The rule includes something called "equivalent facilitation." You don't have to follow WCAG 2.1 exactly if you can prove your alternative provides the same or greater accessibility .

This matters for future standards. If WCAG 3.0 eventually becomes the standard, governments could adopt it early. The flexibility exists so innovation isn't locked to a single version .

But the burden of proof is on you. You need to demonstrate equivalent access, not just claim it.

What happens if you don't comply

The regulations include an undue burden defense. If compliance would fundamentally alter your service or create undue financial and administrative burdens, you don't have to comply fully .

But here's the catch. The decision must be made by the head of the public entity or their designee, after considering all available resources. It must be in writing with reasons. And you still have to provide access to the maximum extent possible without causing undue burden .

This isn't a loophole for ignoring accessibility. It's a narrow exemption for extreme cases, with documentation requirements that most entities won't want to deal with.

The minimal impact provision

There's also a provision for noncompliance that has minimal impact on access. If you're not fully compliant but can demonstrate that the issues don't affect users' ability to access information, engage in interactions, conduct transactions, or participate in programs with substantially equivalent timeliness, privacy, independence, and ease of use, you might be deemed compliant .

The key phrase is "substantially equivalent." If your mobile site has missing alt text on decorative images but all functional content works, that's probably fine. If your checkout flow is broken for screen reader users, that's not minimal impact.

The Fashion Nova warning

The DOJ's February 2026 statement of interest in the Fashion Nova case is worth reading .

The proposed settlement would have paid $2.43 million to California class members and $2.52 million in attorneys fees. Fashion Nova agreed to modify its website "as needed" to achieve substantial conformance with WCAG 2.1.

The DOJ objected. They said the injunctive relief wouldn't meaningfully increase access. There were no concrete steps, no monitoring mechanism, no enforcement .

And in a detail that should embarrass everyone involved, the settlement administrator's own website where blind individuals had to submit claims was inaccessible to screen reader users. The DOJ hired a consultant who documented various barriers .

The DOJ also noted that Class Counsel had filed the same lawsuit in over 500 cases between 2019 and 2023, with most ending in confidential individual settlements .

The message: Courts and the DOJ are watching how settlements are structured. Paying money isn't enough. Actual accessibility improvements are required.

Mobile-first development actually helps

If you build mobile-first with accessibility in mind, desktop accessibility becomes easier. The constraints of small screens force good habits.

Proper heading structure matters more when screen space is limited. Sufficient color contrast is essential in bright sunlight. Large touch targets benefit everyone, not just users with motor impairments.

The W3C's Mobile Accessibility Task Force is actively updating guidance on applying WCAG 2.2 to mobile apps . This work continues even as WCAG 3 development proceeds.

What to do before the deadlines

The DOJ's "First Steps" guide suggests practical actions .

First, learn the requirements. Read the Small Entity Compliance Guide. Understand WCAG 2.1 Level AA.

Second, figure out your deadline based on population. Don't guess. Check Census data.

Third, identify who's responsible. Web developers matter, but so do procurement staff who buy third-party tools. Set clear expectations. Document roles.

Fourth, assess current accessibility. Test your site and mobile apps against WCAG 2.1. Use automated tools but don't rely on them entirely. Manual testing with screen readers and keyboard-only navigation catches what automated tools miss.

Fifth, plan remediation. Prioritize high-impact issues. Fix navigation, forms, and core transactions first. Decorative content can wait.

Sixth, train staff. Accessibility isn't a one-time project. New content needs to be accessible from the start.

The vendor trap

The rule explicitly covers content provided through contractors . If a city contracts with a company to run a parking payment app, that app must be accessible. The city can't blame the vendor.

This means procurement processes need to include accessibility requirements. RFPs should specify WCAG 2.1 AA compliance. Contracts should include enforcement mechanisms. Acceptance testing should verify accessibility before payment.

Small governments with limited resources can use this as leverage. Vendors who want government contracts need to demonstrate accessibility expertise. The market is shifting, and vendors who can't deliver accessible solutions will lose business.

The cost question

Remediation costs real money. The DOJ acknowledges this in the exceptions for undue burden . But the cost of doing nothing is higher.

The Seattle Public Schools case budgeted $665,000 to $815,000 for remediation, training, and hiring an accessibility coordinator. That's after getting sued.

Proactive remediation costs less than reactive litigation. And the deadlines are fixed. April 2026 for large entities. April 2027 for smaller ones. The clock is running.

What WCAG 2.1 Level AA actually requires

There are 50 success criteria at Level A and AA combined. Some are straightforward. Some require interpretation.

Perceivable: Provide text alternatives for non-text content. Provide captions for videos. Present content in different ways without losing meaning. Make it easier for users to see and hear content .

Operable: Make all functionality available from a keyboard. Give users enough time to read and use content. Don't design content in ways that cause seizures. Help users navigate and find content .

Understandable: Make text readable and understandable. Make content appear and operate in predictable ways. Help users avoid and correct mistakes .

Robust: Maximize compatibility with current and future user tools, including assistive technologies .

Each success criterion has specific testable requirements. For mobile, the touch target size requirement from WCAG 2.2 is particularly important. Buttons need enough space that users don't accidentally tap the wrong thing .

The bottom line

Responsive design isn't accessibility. It's a starting point.

The DOJ rule gives clear requirements and deadlines. WCAG 2.1 Level AA is the standard. Mobile apps are covered. Vendor-provided content is covered. Exceptions exist but are narrow.

If you're a state or local government, you need to be compliant by April 2026 or April 2027 depending on your size. That's not far away.

If you're a business, the Title II rule doesn't directly apply to you. But it establishes what the DOJ considers the appropriate technical standard. Private lawsuits under Title III will continue using WCAG as the de facto standard. Courts will look at what the DOJ requires of governments and apply similar reasoning to commercial sites.

The Husqvarna settlement and Fashion Nova case show that courts and the DOJ are paying attention. Settlements that don't produce actual accessibility improvements face scrutiny. Attorneys fees that dwarf class member payments face opposition.

Start testing your responsive site with keyboard-only navigation at 400 percent zoom. Watch a screen reader user try to complete a purchase on their phone. Fix what breaks.

The deadlines are fixed. The requirements are published. The only question is whether you'll be ready.