Columbia, Missouri Website Accessibility Law Guide

Technology and Data Missouri 3 Minutes Read ยท published February 21, 2026 Flag of Missouri

Columbia, Missouri requires municipal websites and public-facing digital services to be accessible to people with disabilities under applicable law and city practice. This guide explains how Columbia approaches WCAG and ADA-related obligations, how to report accessibility barriers, the departments responsible for compliance, and practical steps for site owners and contractors working with the city.

Overview of Legal Framework

Local obligations in Columbia are implemented alongside federal civil-rights law (Title II of the ADA) and often reference technical standards such as the Web Content Accessibility Guidelines (WCAG). Where Columbia has specific procedures or grievance steps, those are managed by the city ADA coordinator and relevant departments. For city-specific complaint routes and accommodation contacts, see the city ADA page [1].

Contact the city ADA coordinator early if your service or site is used by the public.

Who Must Comply

  • City departments and agencies that operate public websites and portals.
  • Contractors and vendors delivering public-facing digital services for the city.
  • Nonprofit or partner organizations when required by city contracts or funding agreements.

Standards and Expectations

Columbia expects public web services to follow recognized accessibility standards such as WCAG 2.1 AA where feasible, and to provide reasonable accommodations under the ADA. Specific technical thresholds or an absolute city-wide WCAG adoption clause is not specified on the cited page [1].

Document accessibility work and remediation timelines for auditability.

Penalties & Enforcement

Enforcement for web accessibility in Columbia is handled through administrative complaint channels and, where applicable, municipal corrective procedures. Monetary fines specifically for web accessibility are not listed on the cited city ADA page; see the footnote for the city contact and grievance procedure [1].

  • Fine amounts: not specified on the cited page.
  • Escalation: first, repeat, or continuing offence ranges are not specified on the cited page.
  • Non-monetary sanctions: corrective orders, mandated remediation plans, and project hold or contract remedies may be used though specific measures are not itemized on the cited page.
  • Enforcer and complaint pathway: City ADA coordinator and the city complaint/grievance process; submit accessibility complaints or accommodation requests via the city ADA contact page [1].
  • Appeals and review: appeal routes and time limits are not specified on the cited page; complainants may request review through city administrative channels or pursue external remedies under federal law.
  • Defences and discretion: documented good-faith efforts, requests for reasonable accommodation, and approved variances or timelines may be considered; specific defenses are not detailed on the cited page.
If enforcement details are critical to your case, request the city grievance procedure and timelines in writing.

Applications & Forms

The city publishes an ADA contact/grievance route; a specific online ADA accommodation form is not specified on the cited page. For procurement or contract-related accessibility requirements, follow contract provisions and request any required forms from the contracting department [1].

Compliance Checklist

  • Perform an accessibility audit using WCAG 2.1 AA test cases.
  • Remediate identified issues with semantic HTML, ARIA where appropriate, and keyboard access.
  • Maintain records of tests, fixes, and user complaints for at least the contractually required retention period.
  • Publish an accessibility statement and a clear contact method for accommodations.
  • Train content editors and procurement staff on accessibility requirements.

Action Steps

  • Audit: Run automated and manual accessibility tests and produce a prioritized remediation plan.
  • Remediate: Fix high-impact issues first (keyboard navigation, form labels, meaningful link text).
  • Document: Keep records of fixes and user requests for accommodations.
  • Report: If you are a member of the public, file an accessibility complaint with the City ADA coordinator [1].

FAQ

Do Columbia websites have to meet WCAG?
Columbia follows ADA obligations and expects accessible public services; an explicit city-wide binding WCAG adoption clause is not specified on the cited page [1].
How do I report an inaccessible city web page?
Contact the City ADA coordinator via the city ADA contact/grievance page to report barriers or request accommodation [1].
Can vendors be required to deliver accessible sites for city contracts?
Yes. Contract terms and procurement documents can require accessibility; consult the contracting department for contract-specific forms and clauses.

How-To

  1. Inventory public pages and services that must be accessible.
  2. Run an automated scan and a manual keyboard and screen-reader review.
  3. Prioritize and fix critical barriers (navigation, forms, attachments).
  4. Publish an accessibility statement and contact details for accommodation requests.
  5. Use the city ADA contact to notify the city of unresolved barriers or to request help [1].

Key Takeaways

  • Documented accessibility processes reduce enforcement risk.
  • WCAG-based audits and fixes are practical first steps.

Help and Support / Resources

  1. [1] City of Columbia ADA coordinator and contact page

Categories

General Governance and Administration Public Safety Public Health and Welfare Land Use and Zoning Housing and Building Standards Transportation Environmental Protection Parks and Public Spaces Business and Consumer Protection Taxation and Finance Labor and Employment Education Civil Rights and Equity Elections and Campaign Finance Events and Special Uses Signs and Advertising Utilities and Infrastructure Technology and Data