Website ADA Compliance in Missouri: How to Meet ADA Website Requirements

Website ADA Compliance in Missouri affects any Missouri business or public agency that offers goods or services to the public. This guide explains what federal disability law requires, which web standards judges and regulators use, how to test a site, and the practical steps to fix accessibility problems.

Which laws apply in Missouri

The Americans with Disabilities Act (ADA) is a federal civil rights law that applies nationwide, including Missouri. Title II covers state and local government websites. Title III covers private businesses that are places of public accommodation, such as retail stores, restaurants, hotels and professional services.

There is no single federal regulation that spells out precise web rules. Instead, regulators and courts commonly reference the Web Content Accessibility Guidelines, most often WCAG 2.1 level AA, as the technical standard to meet.

Who must make websites accessible

Public entities

State agencies, counties and cities must provide equal access to programs and services. Accessibility obligations usually extend to online services that replace or supplement in-person services.

Private businesses

Businesses open to the public typically must ensure their websites do not create barriers for people with disabilities. The ADA applies to the goods and services those websites deliver.

Standards and technical basics

WCAG 2.1 provides testable success criteria in three conformance levels: A, AA and AAA. Level AA is the target most organisations use because it balances usability and cost. Common WCAG topics include:

• Keyboard accessibility
• Clear semantic headings and structure
• Text alternatives for images and non-text content
• Forms that include labels and error identification
• Color contrast and readable text sizing
• Accessible ARIA use for dynamic content

Section 508 applies to federal agencies. It references WCAG and other technical rules. State and local governments and private entities usually follow WCAG for web accessibility compliance.

How to audit a Missouri website

Use a mix of automated scans, manual review and assistive-technology testing. Each method finds different problems.

Automated tools (first pass)

• Run at least two automated scanners to locate syntactic issues such as missing alt text and ARIA misuse.
• Automated tools typically find about 20 to 40 percent of accessibility problems. They are fast but not sufficient by themselves.

Manual code and UX review

• Check semantic HTML headings, document language, link text and form labels.
• Test keyboard-only navigation for all interactive controls and dialogs.
• Verify focus order and visual focus indication when tabbing through the page.

Assistive-technology testing

• Test with a screen reader such as NVDA or VoiceOver to confirm content order and label exposure.
• Use mobile screen reader tests for iOS and Android where the site offers mobile features.

User testing

Arrange sessions with people who have disabilities. Real users will reveal barriers that automated tests do not show, such as confusing workflows or poorly labelled controls in complex forms.

Common accessibility problems to prioritise

• Missing or empty alt attributes on meaningful images
• Inaccessible PDF and Word documents
• Poor keyboard accessibility for navigation and interactive widgets
• Insufficient color contrast on text and controls
• Unlabelled or mislabelled form fields and error messages
• Pop-ups and modal dialogs that trap keyboard focus

Step-by-step remediation plan

Use a risk-based approach. Fix the items that block basic access first. Then address more complex interactive features.

Phase 1: Quick wins (0 to 30 days)

• Publish an accessibility statement describing current conformance and contact details.
• Fix obvious failures: missing alt text on key images, broken labels, non-working skip links.
• Convert top public documents into accessible formats or post accessible summaries.

Phase 2: Core fixes (30 to 90 days)

• Repair keyboard navigation and focus management across templates.
• Address color contrast and text sizing across the main content templates.
• Remediate the most used forms and transaction flows end to end.

Phase 3: Ongoing work (90 days and beyond)

• Run regular automated scans and monthly manual checks for high-traffic pages.
• Train content editors to publish accessible content and accessible documents.
• Include accessibility requirements in procurement and vendor contracts.
• Commission periodic user testing with people who have disabilities.

Practical steps if you receive a demand letter or complaint

Missouri organisations commonly face demand letters before litigation. Responding quickly reduces legal risk.

1. Acknowledge receipt and request reasonable time to assess.
2. Run a focused audit of the pages cited by the complainant.
3. Document findings, planned fixes and an estimated timeline.
4. Offer concrete remediation steps and a contact for further communication.
5. Follow through on the remediation and confirm fixes with the complainant.

If the complaint involves a state or federal agency, engage legal counsel experienced in accessibility matters before responding to formal notices.

Common mistakes that slow remediation

• Relying only on automated tools
• Fixing visual presentation without correcting underlying HTML semantics
• Uploading inaccessible PDFs without text alternatives
• Using ARIA incorrectly instead of using native HTML elements
• Not training content authors to create accessible content

Accessibility statement and governance

An accessibility statement should be short and factual. Include the scope, standards used, known limitations and contact details. Update the statement when major changes occur.

Create an internal policy that assigns responsibility for accessibility to a specific role. Track issues in a public or internal log and set review dates for priority pages.

When to hire specialists and what to budget for

Hire an accessibility expert for complex interactive sites, custom web applications and large document libraries. Expect higher costs for extensive JavaScript frameworks or third-party widgets that need custom work.

Ask prospective vendors for examples of published accessibility remediations and references. Confirm they test with assistive technology and real users.

Checklist for Website ADA Compliance in Missouri

• Run an automated scan and keep the report
• Complete manual keyboard and screen reader checks on core pages
• Publish or update an accessibility statement with contact details
• Remediate high-impact defects in 30 to 90 days
• Train authors and include accessibility in procurement
• Set a schedule for re-tests and periodic user testing

Next steps

Start with a short audit of the homepage, contact page and any transactional forms. That gives a clear picture of risk and helps you estimate cost and time. If legal notices are already in play, prioritise response and immediate fixes to the pages named in the notice.

If you want, I can outline a 30- or 90-day remediation timetable for your specific site. Share the site URL and the top three pages you want prioritised.