Chattanooga WCAG Website Compliance Checklist

Technology and Data Tennessee 3 Minutes Read · published February 20, 2026 Flag of Tennessee

This checklist helps Chattanooga, Tennessee web teams and contractors align municipal websites with WCAG accessibility standards. It explains steps to assess pages, remediate common barriers, document compliance, and report or appeal enforcement actions. The guidance focuses on actionable tasks for site owners responsible to the city and points to official municipal code and reporting channels for complaints and follow-up.

Assessment & Planning

Begin with a baseline audit that maps site areas (public-facing content, forms, payments, documents) to WCAG 2.1 AA success criteria. Track issues by URL, affected criteria, severity, and remediation owner. Prioritize live public services and legally required information pages.

  • Run automated scans and manual keyboard and screen-reader tests.
  • Set a remediation timeline with milestone dates and owners.
  • Inventory PDFs and documents for format conversion or accessible alternatives.
Start audits with high-traffic services first to reduce public access barriers.

Technical Remediation

Fix root causes: semantic HTML, ARIA roles only when necessary, keyboard focus order, descriptive link text, captions/transcripts for media, and accessible form labels and error handling. Use a versioned accessibility statement on the site describing conformance level, testing methods, known exceptions, and contact instructions.

  • Prioritize code changes over overlays; document accepted exceptions.
  • Retest after fixes with both automated and manual checks.
  • Keep accessible source documents for public records and uploads.

Penalties & Enforcement

Municipal enforcement for noncompliant city websites follows the city's code and administrative processes for communications and public information; specific web-accessibility fines or statutory dollar amounts are not specified on the cited municipal pages. Responsibility for receiving complaints and initiating follow-up typically lies with city code or administrative offices and the designated city complaint intake system. Municipal Code[1]

  • Fine amounts: not specified on the cited page.
  • Escalation for repeat or continuing offences: not specified on the cited page.
  • Non-monetary sanctions: administrative orders, correction notices, or referral to legal counsel are typical remedies; specific remedies for websites are not specified on the cited page.
  • Enforcer and complaints: City complaint intake and records channels handle reports; file a complaint through the city's official intake page. Report a Concern[2]
  • Appeals and review: procedure and time limits for appeals are not specified on the cited municipal code page; check the cited municipal code or contact city intake for process and deadlines.
If you receive a notice, document all remediation and communications to support any appeal.

Applications & Forms

No city-specific web-accessibility compliance form is published on the cited municipal pages; submission typically uses the city's complaint intake or records request channels cited above. Municipal Code[1]

Action Steps for Municipal Webmasters

  • Conduct a full-site audit within 30-90 days depending on site size.
  • Prioritize fixes for payments, forms, and transit/public safety information.
  • Publish an accessibility statement and contact method for reporting issues.
  • Budget for remediation and ongoing QA in procurement for vendors and contractors.
Document fixes with screenshots, test logs, and dates to show good-faith remediation.

FAQ

Who enforces web accessibility for Chattanooga city websites?
The city complaint intake and relevant administrative offices review reports and coordinate remediation; specific enforcement authority and penalties are detailed in the municipal code cited above. Municipal Code[1]
How do I report an inaccessible page?
File a report through the City of Chattanooga complaint intake system; include the page URL, device/browser used, and a brief description of the barrier. Report a Concern[2]
Are there required WCAG levels for city sites?
The city references accepted accessibility standards for web content but the municipal code page does not specify a required WCAG level; see the city's published accessibility statement or contact intake for current policy.

How-To

  1. Run an automated accessibility scan of the entire site and export results.
  2. Complete manual checks: keyboard navigation, focus order, and screen-reader review for critical pages.
  3. Prioritize and assign remediation tasks with deadlines and owners in a tracking sheet.
  4. Retest pages after remediation and record test artifacts.
  5. Publish or update an accessibility statement with contact info and remediation timelines.
  6. Respond to reports filed through city intake and document corrective actions.

Key Takeaways

  • Audit, remediate, and document—start with high-priority public services.
  • Publish a clear accessibility statement and reporting method.
  • Use the city's official intake channel to report inaccessible pages for official follow-up.

Help and Support / Resources

  1. [1] City of Chattanooga municipal code - Municode
  2. [2] City of Chattanooga Report a Concern (311)

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