Why this matters to private-sector owners
Minnesota updated its digital-accessibility standard to WCAG 2.1 Level AA effective July 1, 2024. While the mandate applies directly to state agencies, it signals where enforcement is headed, and it raises visitor expectations for every site in the state. (mn.gov // Minnesota’s State Portal)
Courts are already expanding liability. A recent Minnesota federal ruling held that web-only businesses can be sued under the ADA’s Title III, even without a physical storefront. (Employment Law Lookout) Meanwhile, plaintiffs’ firms filed over 1,100 accessibility lawsuits last year alone, often targeting small companies that didn’t know they were at risk. (The Wall Street Journal)
- 1,100+
- Accessibility lawsuits filed last year
- $150K
- Average settlement cost
- 15%
- Of people have disabilities
Bottom line: adopting WCAG 2.1 isn’t just good practice, it’s insurance against six-figure legal headaches.
The 30-item WCAG 2.1 Level AA checklist
Use this comprehensive checklist to ensure your website meets the WCAG 2.1 Level AA standards.
1. Perceivable
- Every meaningful image has descriptive alt text. WCAG 1.1.1. Quick test: turn off images in your browser.
- All pre-recorded videos include captions. WCAG 1.2.2. Quick test: play with captions toggled.
- Videos with spoken content have audio descriptions or transcripts. WCAG 1.2.5. Quick test: listen without visuals.
- Headings follow a logical h1 to h6 order. WCAG 1.3.1. Quick test: use browser outline.
- Normal-text color contrast is at least 4.5:1; large-text at least 3:1. WCAG 1.4.3. Quick test: run a contrast checker.
- Info is not conveyed by color alone (e.g., error text plus icon). WCAG 1.4.1. Quick test: print in grayscale.
- Text can be zoomed 200% with no loss of content. WCAG 1.4.4. Quick test: Ctrl/Cmd + twice.
- Form fields have visible labels (not placeholders only). WCAG 1.3.1 / 3.3.2. Quick test: tab to each input.
- No auto-playing audio longer than 3 seconds, or user can stop it. WCAG 1.4.2. Quick test: load page with speakers on.
- Links are descriptive (“View pricing”, not “Click here”). WCAG 2.4.4. Quick test: tab through links.
2. Operable
- Entire site is keyboard-navigable. WCAG 2.1.1. Quick test: unplug mouse and test.
- Visible focus indicator on interactive elements. WCAG 2.4.7. Quick test: tab key highlights.
- No keyboard traps (you can tab in and out of modals). WCAG 2.1.2. Quick test: Shift-Tab back out.
- “Skip to main content” link present. WCAG 2.4.1. Quick test: focus appears at top.
- Users can pause, stop, or hide sliders and animations. WCAG 2.2.2. Quick test: hit Esc / Pause.
- Navigation order is logical and consistent. WCAG 2.4.3 / 3.2.3. Quick test: tab through pages.
- Touch targets at least 44 by 44 px on mobile. WCAG 2.5.5. Quick test: measure in dev tools.
- Motion-triggered interactions have an alternative. WCAG 2.5.1. Quick test: shake device test.
- No content flashes more than 3 times per second. WCAG 2.3.1. Quick test: watch any animations.
- Form errors are identified and described in text. WCAG 3.3.1. Quick test: submit blank form.
3. Understandable
- Language attribute set (
<html lang="en">). WCAG 3.1.1. Quick test: view page source. - Reading level is clear: avoid jargon, explain acronyms. WCAG 3.1.5. Quick test: Hemingway grade 9 or lower.
- Navigation, icons, and buttons are consistent site-wide. WCAG 3.2.3. Quick test: compare pages.
- Inputs use autocomplete where possible. WCAG 1.3.5. Quick test: browser autofill.
- No unexpected context changes on focus (e.g., auto submit). WCAG 3.2.1. Quick test: tab through menu.
4. Robust
- HTML validates (no critical errors). WCAG 4.1.1. Quick test: W3C validator.
- ARIA roles and labels used only when native elements won’t do. WCAG 4.1.2. Quick test: inspect element.
- Status messages (e.g., “Added to cart”) announced to screen readers. WCAG 4.1.3. Quick test: use NVDA “speech viewer”.
- Content survives CSS and JS disabled (graceful degradation). WCAG global. Quick test: disable each in dev tools.
- Site tested with at least one screen reader (NVDA, VoiceOver). WCAG holistic. Quick test: navigate key pages.
Next steps for Minnesota and Oregon businesses
- 01
Audit
Run an automated scan (Lighthouse, WAVE) to spot quick wins, then manual-check the rest.
- 02
Fix
Prioritize issues with legal impact (contrast, alt text, keyboard traps).
- 03
Document
Keep a remediation log; it shows good-faith effort if you're ever sued.
- 04
Train
Make accessibility part of your dev workflow: linting, design-system components, code review checkpoints.
- 05
Monitor
Re-test quarterly and after every major release.