Charleston Website Accessibility Ordinance & WCAG Guide

Technology and Data South Carolina 3 Minutes Read · published February 21, 2026 Flag of South Carolina

Charleston, South Carolina requires public-facing municipal websites and digital services to meet accessibility expectations under applicable public accommodation and government access standards. This guide explains how local rules, municipal policy, and federal ADA expectations intersect with WCAG guidelines, how to report barriers, and practical steps for local businesses and contractors working with the city to reduce legal and operational risk.

If you manage a Charleston public website, document accessibility checks and remediation timelines.

Scope and Legal Basis

The City of Charleston provides a municipal code and official policies that govern city operations; website accessibility obligations for the city itself are set by municipal policy and applicable federal law. For private businesses and third parties, federal accessibility obligations under the Americans with Disabilities Act (ADA) and state nondiscrimination laws commonly apply to public accommodations and government contractors.

For municipal code and official city documents, consult the City of Charleston Code of Ordinances.[1] For the city’s published accessibility statement and contact for reporting web barriers, see the City of Charleston accessibility page.[2] Federal enforcement guidance on public entity obligations under Title II of the ADA is available from the U.S. Department of Justice.[3]

Practical WCAG Expectations

Charleston does not publish a separate municipal WCAG standard beyond adopting applicable federal accessibility obligations; in practice, municipal websites and digital services follow WCAG 2.1 AA as the technical benchmark used by many public entities and courts. Owners and vendors should adopt written accessibility plans, test with both automated tools and human review, and maintain an issue log with remediation dates.

  • Documented accessibility policy and contact information.
  • Regular testing schedule (automated monthly, manual audit annually).
  • Remediation timelines prioritized by impact and usage.
Keep an accessible-staging environment to validate fixes before production deployment.

Penalties & Enforcement

Enforcement for website accessibility issues affecting city digital services typically proceeds through internal city reporting and federal complaint channels rather than fixed municipal civil fines. Specific monetary fines for failure to comply with web accessibility are not specified on the cited municipal pages; federal remedies may include injunctive relief and damages where the ADA authorizes them, but monetary amounts depend on the enforcement instrument and court decisions, not a city ordinance posting.[1]

  • Fine amounts: not specified on the cited city pages; federal remedies vary.
  • Escalation: typically initial report, remediation request, then administrative or federal complaint if unresolved.
  • Non-monetary sanctions: injunctive orders, required remediation plans, and potential contract suspension for vendors.
  • Enforcer: City departments for city sites; U.S. Department of Justice for Title II complaints; city accessibility contact handles reports and initial intake.[2]
  • Appeals/review: appeal routes are not specified on the cited municipal pages; federal processes follow DOJ administrative or court procedures.
If a remediation timeline is missed, document all communications and escalate to the city accessibility contact and federal channels if needed.

Applications & Forms

No dedicated municipal form for web accessibility complaints is published on the city’s accessibility page; reports are accepted via the city’s listed contact points and standard complaint intake processes.[2]

  • Form name/number: none published on the cited page.
  • Submission method: use the city’s accessibility contact or department complaint channels as listed on the official page.

Action Steps for Website Owners

  • Conduct an accessibility audit against WCAG 2.1 AA.
  • Publish an accessibility statement with contact details and remediation timelines.
  • Budget for remediation and continuous testing in procurement contracts.

FAQ

Who enforces website accessibility for city-owned websites?
The city’s accessibility contact and relevant departments handle internal compliance; federal enforcement may be pursued under ADA Title II through the U.S. Department of Justice.[3]
Can private businesses be fined by the city for inaccessible websites?
The cited city pages do not specify municipal fines for private websites; private businesses are primarily subject to federal ADA enforcement and state law remedies where applicable.[1]
How do I report an accessibility barrier on a Charleston website?
Report using the contact information on the City of Charleston accessibility statement or the department page responsible for the site; if unresolved, a federal complaint route exists with the DOJ.[2]

How-To

  1. Locate the website’s accessibility statement or contact details.
  2. Document the barrier with screenshots, URLs, and steps to reproduce.
  3. Send a clear report to the city contact and request an estimated remediation timeline.
  4. If no timely remediation, consider filing a federal complaint under ADA Title II with the DOJ.

Key Takeaways

  • Charleston relies on municipal policy and federal ADA expectations; WCAG 2.1 AA is the practical benchmark.
  • Document issues, report to the city accessibility contact, and keep remediation records.
  • Monetary fines are not specified on city pages; remedies often aim at remediation and injunctive relief.

Help and Support / Resources


  1. [1] City of Charleston Code of Ordinances
  2. [2] City of Charleston Accessibility Statement
  3. [3] U.S. Department of Justice - ADA Title II