Chicago Website Accessibility Law & WCAG Guide

Technology and Data Illinois 3 Minutes Read · published February 04, 2026 Flag of Illinois

Chicago, Illinois requires public access to municipal information and increasingly expects city-related websites and services to follow accessibility standards such as WCAG. This guide explains practical steps, municipal responsibilities, complaint routes and how to prioritize fixes for web content and digital services used by Chicago residents.

Start by auditing public-facing pages against WCAG 2.1 AA and documenting user journeys.

Overview

Municipal obligations for website accessibility in Chicago arise from a mix of federal law (Americans with Disabilities Act), state accessibility standards, and city accessibility policies and statements. City agencies must balance technical standards (WCAG), procurement rules and resident-facing commitments. This article focuses on actionable steps for city departments, vendors and contractors working on Chicago-related web services.

Penalties & Enforcement

Formal monetary fines for website accessibility specifically are not widely articulated in a single Chicago municipal code provision; specific fine amounts are often not specified on typical municipal accessibility pages or federal guidance and may depend on the enforcing authority and remedy sought. Enforcement pathways can include administrative complaints, civil enforcement, settlement agreements and court actions brought under federal or state disability laws.

  • Enforcer: enforcement may involve City of Chicago departments together with the City Department of Law or outside agencies depending on the claim; the Chicago Commission on Human Relations sometimes handles discrimination complaints.
  • Inspection and complaint pathways: complaints typically start through an agency accessibility contact or general complaints portal and may escalate to formal administrative or court processes.
  • Fine amounts: not specified on the cited page.
  • Escalation: first, remediation requests or settlement negotiations; repeated or continuing violations can lead to litigation or injunctive relief, but specific escalation schedules are not specified on the cited page.
  • Non-monetary sanctions: common remedies include orders to remediate, injunctive relief requiring accessibility fixes, consent decrees, and requirements to post accessibility statements or provide alternative formats.
If a precise fine or section number is required, request the enforcing department to cite the controlling ordinance or statute.

Applications & Forms

For web accessibility issues the City often does not publish a dedicated universal form; complaints and requests for assistance are generally submitted through department accessibility contact pages or general customer service/complaint portals. If a specific accessibility remediation program or vendor onboarding form exists for an agency it will be published on that agency's official site.

Practical Compliance Steps

Follow these prioritized steps to align Chicago-facing web properties with WCAG and municipal expectations.

  • Conduct an accessibility audit using automated tools and manual testing with assistive technologies.
  • Document issues in a remediation plan that assigns priority, owner and deadlines.
  • Implement fixes by code, CMS configuration, or content changes and validate with users with disabilities.
  • Maintain records of tests, fixes, and communications to demonstrate good-faith compliance efforts.
  • Include accessibility requirements and acceptance criteria in procurement contracts with vendors.
Accessibility is an ongoing program, not a one-time project.

Common Violations and Typical Remedies

  • Missing alt text and non-descriptive links — remedy: update attributes and link text.
  • Insufficient color contrast — remedy: adjust colors or provide alternate presentation options.
  • Non-keyboard-accessible controls — remedy: ensure keyboard focus and ARIA where appropriate.
  • Uncaptioned multimedia — remedy: add captions or transcripts.

FAQ

Who enforces website accessibility for Chicago city services?
The City, through its departments and legal offices, can respond to complaints; federal or state agencies may also be involved for statutory claims.
Which WCAG level should Chicago websites aim for?
WCAG 2.1 AA is a commonly adopted target for public-facing government sites and provides a practical balance of accessibility and technical feasibility.
How do I report an inaccessible City web page?
Report via the department's accessibility/contact page or the City's general complaints portal; include page URL, issue description and contact information for follow-up.

How-To

  1. Run an automated accessibility scan of the site to find obvious errors.
  2. Perform manual tests with keyboard navigation and a screen reader on representative pages.
  3. Create a prioritized remediation plan that lists pages, issues, owner and deadlines.
  4. Fix issues in staging, validate fixes, and deploy with notes documenting completed work.
  5. Publish an accessibility statement and a clear reporting contact so users can request help or file complaints.
Keep a public accessibility statement that explains standards, exceptions and contact details.

Key Takeaways

  • Target WCAG 2.1 AA for most public-facing Chicago web services.
  • Document audits and remediation to show good-faith compliance efforts.
  • Provide clear reporting channels for users to submit accessibility complaints.

Help and Support / Resources

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