Back to reviews and guides

Website ADA Compliance in Louisiana: What Businesses Should Know

Practical guide for Louisiana businesses on website ADA compliance, including who must comply, WCAG targets, how to audit and fix sites. It gives a remediation roadmap, a checklist for responding to complaints, and an accessibility statement template.

Website ADA Compliance in Louisiana matters for any organisation that serves the public. This guide explains who must comply, which accessibility standard to aim for, how to test and fix a site, and what to do if you get a complaint or demand letter.

Who must comply in Louisiana

The Americans with Disabilities Act is federal. That means it applies across Louisiana. Two parts are most relevant to websites.

Public entities (Title II)

State and local government bodies must provide programs and services that are accessible. That includes websites and web-based tools used to deliver services.

Places of public accommodation (Title III)

Private businesses that serve the public are generally covered. Examples are retail, hospitality, healthcare, finance and education providers open to customers. Courts and agencies consider websites part of the service those businesses provide.

Which accessibility standard to use

Most lawyers, accessibility specialists and courts point to the Web Content Accessibility Guidelines. The common target is WCAG 2.1 AA. It sets measurable success criteria such as:

  • Colour contrast: 4.5:1 for normal text, 3:1 for large text
  • Text alternatives for images
  • Keyboard operability and visible focus indicators
  • Captions for prerecorded video and transcripts for audio

How to check your site: an audit you can follow

Combine automated scans, manual review and testing with real users. Each method finds different problems.

Automated testing (first pass)

  • Use at least one established tool such as axe, WAVE or Lighthouse to find common issues.
  • Run scans on main templates: homepage, product page, forms, checkout and account pages.
  • Export results and prioritise by severity and user impact.

Manual testing (required)

  • Keyboard test: can every interactive control be reached and used without a mouse?
  • Screen reader test: try a free screen reader such as NVDA on Windows or VoiceOver on macOS.
  • Semantic HTML review: check heading order, landmark elements, form labels and ARIA only where necessary.

User testing

Test with at least one person who has a disability. Even short sessions reveal real-world barriers that tools miss.

Step-by-step remediation roadmap for Louisiana businesses

Use this practical sequence. Time and cost vary by site complexity and platform.

Phase 1 — rapid risk reduction (1–4 weeks)

  • Fix critical barriers that block access, for example missing alt text on primary images, broken form labels, and keyboard traps.
  • Add an accessible contact method on the homepage and accessibility statement placeholder.
  • Document findings and create a project plan.

Phase 2 — full compliance work (4–12+ weeks)

  • Remediate templates and components to meet WCAG 2.1 AA criteria.
  • Update content: captions, transcripts and semantic HTML.
  • Repeat automated and manual testing after each major change.

Phase 3 — verification and ongoing work

  • Run a formal accessibility audit and document test results.
  • Set up monitoring and a content accessibility workflow for editors.
  • Plan periodic user testing and staff training.

Common fixes that deliver the biggest benefit

  • Images: add descriptive alt text and mark decorative images with empty alt attributes.
  • Forms: add explicit <label> elements or aria-label attributes and clear error messages.
  • Navigation: ensure logical heading order and keyboard focus order; add skip links.
  • Media: provide captions for video and transcripts for audio.
  • Colour: meet WCAG contrast ratios and do not rely on colour alone to convey meaning.
  • ARIA: use only when native HTML cannot solve the problem and test with assistive technologies.

Responding to a demand letter or complaint

Don’t ignore a demand letter. Respond calmly and document the steps you take. Below is a simple checklist to follow immediately.

  • Confirm receipt and state you take access seriously.
  • Engage counsel experienced in ADA web matters.
  • Run a focused accessibility audit of the pages cited in the letter.
  • Implement high-impact fixes quickly and record timelines.
  • Offer a remediation timeline and accessible contact method in writing.

These actions show good-faith efforts. That often affects negotiation and outcomes.

Accessibility statement and policy

An accessibility statement explains what you aim to do and how people can contact you. Include a clear contact method and an outline of your remediation process.

Short template to adapt

This is an example you can adapt for your site.

<strong>Accessibility statement</strong> We aim to make our website accessible. We follow WCAG 2.1 AA where possible. If you need assistance using the site, contact us at [email or phone]. We respond to accessibility requests within [number] business days.

Ongoing maintenance, procurement and training

Accessibility is not a one-off. Add these practices to reduce future risk.

  • Procurement: require accessibility as a criterion when buying software, themes or plugins.
  • Content workflow: train editors to check alt text, headings and link text before publishing.
  • Monitoring: run automated scans monthly and manual checks quarterly.
  • Training: provide basic accessibility training for developers and content authors.

When to get expert help

Hire an accessibility auditor or developer when:

  • Your site has complex interactive components or custom applications.
  • You have received formal legal notice or a lawsuit.
  • You need an accessibility statement and verification report for risk management.

Next steps for Louisiana businesses

Start with a short automated scan and the keyboard test. If issues appear, create a remediation plan and set priorities. If you receive a complaint, respond quickly and document your actions.

Good practice protects users and reduces legal risk. Take one concrete step this week: run a scan or book a short user test with someone who uses assistive technology.