Back to reviews and guides

Website ADA Compliance in Michigan: A Practical Guide for Businesses

This practical guide explains how federal ADA rules apply in Michigan, the WCAG 2.1 AA standard most organisations use, and a step-by-step remediation roadmap. It includes testing methods, a timeline, common mistakes, an accessibility statement template, and next steps if you receive a demand letter.

Website ADA Compliance in Michigan matters for many businesses. This guide explains why federal ADA rules apply in Michigan, how to check your site, the practical steps to fix problems, and what to do if you get a demand letter.

Does the ADA apply to websites in Michigan?

Title III of the Americans with Disabilities Act is a federal law that applies in every state, including Michigan. Courts and settlements have interpreted that businesses open to the public often must make digital services accessible. The technical standard most courts and accessibility professionals use is WCAG 2.1 level AA.

Which Michigan organisations should prioritise website accessibility?

  • Businesses with a public-facing website that links to a physical store or provides services to the public.
  • Government and public agencies, which typically face stricter accessibility expectations.
  • Online-only businesses should still assess risk. Many courts focus on the connection between a website and a physical place of public accommodation.

Quick test: how to tell if your site is likely non-compliant

  • Images without alternative text.
  • Interactive controls that can’t be used with keyboard alone.
  • Poor colour contrast for normal text (WCAG AA requires 4.5:1 for normal text).
  • Videos without captions or transcripts.
  • PDFs and documents that are not tagged for accessibility.

Practical compliance checklist for Michigan businesses

Use this ordered checklist as a remediation roadmap. Start at the top and work down.

  1. Audit — Run automated scans, keyboard tests, and at least one screen reader pass.
  2. Prioritise fixes — Fix broken navigation, missing alt text, and keyboard barriers first.
  3. Fix templates and patterns — Update header structure, forms, buttons, and ARIA where needed.
  4. Address media — Add captions, transcripts, and audio descriptions when required.
  5. Remediate documents — Convert or tag PDFs and Word files so they are accessible.
  6. Test with users — Recruit people with disabilities for real-world testing.
  7. Publish an accessibility statement — State the WCAG target, current status, and contact for feedback.
  8. Monitor — Add accessibility checks to QA and deploy periodic audits.

How to test — tools and methods

Combine automated tools with manual checks and people testing.

  • Automated tooling: run a scanner to catch obvious failures.
  • Keyboard testing: navigate the entire site using only the keyboard.
  • Screen reader testing: test key journeys with NVDA on Windows and VoiceOver on Apple devices.
  • User testing: include at least two people who use assistive technology for core tasks like purchase or contact.

Common mistakes Michigan businesses make

  • Relying only on automated scans. Automated tools find about 20 to 50 percent of issues.
  • Failing to test forms and checkout flows with a keyboard and a screen reader.
  • Uploading untagged PDFs and hoping users can read them.
  • Using CAPTCHA that offers no accessible alternative.
  • No ownership: leaving accessibility to one developer without governance.

Remediation plan with a simple timeline

Adapt this plan to your team size and site complexity.

  • Week 1: Run a full audit and document issues by priority.
  • Weeks 2 to 6: Fix high-priority issues affecting navigation, forms, and media.
  • Weeks 6 to 12: Remediate templates, legacy pages, and documents.
  • Month 3 onward: User testing, publish accessibility statement, and add ongoing checks to QA.

Decision framework: in-house or hire a vendor?

Choose based on skills, time, and risk.

  • Keep it in-house when you have a front-end developer familiar with semantic HTML, ARIA, and WCAG.
  • Hire a specialist when you lack experience, the site is large, or there is pending litigation.
  • Contract terms to require: target WCAG level, remediation timeline, acceptance tests, and a post-remediation warranty period.

What to do if you receive a demand letter or lawsuit

  • Do not ignore the letter. Note the deadline and preserve communications and site versions.
  • Engage a Michigan attorney experienced with ADA matters to advise on next steps.
  • Start an independent accessibility audit immediately and document fixes.
  • Consider offering a remediation plan and timeline to the complainant where appropriate.

Accessibility statement template (adapt for your business)

Use this short starting point. Tailor the details and contact information.

We aim to make our website accessible. Our target standard is WCAG 2.1 level AA. If you have difficulty using this site or need assistance, please contact us at [email or phone] and we will help. This statement is not a legal guarantee.

Costs and resources

Costs vary with site size, complexity, and whether you use in-house staff or outside experts. Expect ongoing costs for monitoring and content updates. Useful resources include the W3C WCAG documentation, screen reader user guides, and accessibility testing tools.

Where to find help in Michigan

Look for accessibility consultants, web development agencies with accessibility experience, and local disability organisations for user testers. For legal questions, contact a Michigan lawyer who specialises in ADA and accessibility law.

Final checklist before you go live

  • Automated scan completed and critical issues fixed.
  • Keyboard and screen reader checks of main user journeys.
  • Captions or transcripts for video content.
  • Tagged PDFs or HTML alternatives for documents.
  • Accessibility statement with contact details published.
  • Ongoing monitoring plan in place.

If you want, I can suggest a starter audit script for your site or a checklist your developer can use. Tell me your site type and one core user journey to begin.