Raleigh Website Accessibility - WCAG & City Ordinance

Technology and Data North Carolina 3 Minutes Read ยท published February 08, 2026 Flag of North Carolina

Raleigh, North Carolina requires public-facing websites operated by the city and many city contractors to follow recognized accessibility standards. This guide explains how Raleigh entities can align with WCAG, where municipal authority and complaint pathways sit, and the practical steps to audit, remediate, and document compliance.

Penalties & Enforcement

The City of Raleigh's digital accessibility resources describe obligations and reporting routes but do not list explicit monetary fines for web accessibility noncompliance on the cited pages. Enforcement typically involves administrative remediation orders, escalation to department leadership, and referrals to the City Attorney or external civil enforcement if federal ADA claims arise. For official procedures and contact points, see the city accessibility pages and the Raleigh municipal code.Digital Accessibility[1] Raleigh Code of Ordinances[2]

  • Monetary fines: not specified on the cited page; federal remedies may apply where federal law is invoked.
  • Escalation: city remediation orders and repeated noncompliance may lead to legal referral; specific escalation schedules are not specified on the cited page.
  • Non-monetary sanctions: remediation directives, mandatory accessibility plans, removal or disabling of noncompliant content, and legal action via City Attorney or federal court.
  • Enforcer / contact: ADA Coordinator and Information Technology or designated accessibility office listed on the city accessibility page. City Accessibility Contacts[3]
  • Appeals & review: appeal routes are not specified on the cited page; affected parties may seek administrative review or pursue federal ADA processes within applicable statute of limitations.
  • Defences/discretion: documented good-faith remediation plans, available technical exemptions, or approved variances may be considered; specific local variances are not specified on the cited page.
Report accessibility barriers promptly to the city accessibility contact to trigger remediation.

Applications & Forms

The City does not publish a single universal "website compliance" fine or permit form on the cited pages; instead, report requests and accessibility issues through the city's accessibility contact form or service request channels, and submit documentation of remediation plans when requested.[3]

How to achieve WCAG compliance in Raleigh

Follow a clear project plan: audit, remediate, publish an accessibility statement, train content editors, and set ongoing monitoring. The steps below explain common municipal expectations and practical actions for Raleigh entities and vendors.

  1. Conduct an initial accessibility audit against WCAG 2.1 AA (or the level specified by contract).
  2. Create a written remediation plan with timelines, responsibilities, and acceptance criteria.
  3. Prioritize fixes that block access to services and implement code and content changes.
  4. Publish an accessibility statement noting standards, known issues, and contact/reporting information.
  5. Set recurring testing and monitoring, and train content authors on accessible authoring practices.
  6. If disputes arise, use city complaint channels, document communications, and seek review from the ADA Coordinator or legal counsel.
Maintain records of audits and remediation to demonstrate good-faith compliance efforts.

Common violations

  • Missing alternative text for images or complex graphics.
  • Insufficient color contrast on essential UI elements.
  • Nonsemantic headings and improper keyboard focus order.
  • Inaccessible PDFs and documents linked from city sites.

FAQ

How do I report an accessibility problem on a City of Raleigh website?
Use the City of Raleigh accessibility contact or online report form listed on the accessibility pages; include the page URL, device/browser, and a description of the barrier.[3]
Which standard should Raleigh websites meet?
Raleigh references WCAG conformance expectations; check contract or policy documents for the specific required WCAG level (commonly WCAG 2.1 AA). See the city digital accessibility information for details.[1]
What happens after I file a complaint?
The city will review the report, request additional information if needed, and expect remediation or a remediation plan; formal penalties for web accessibility are not specified on the cited pages.

How-To

  1. Run an automated and manual accessibility audit to create a prioritized issue list.
  2. Draft and publish an accessibility statement that lists standards, contact info, and known issues.
  3. Fix high-impact issues first, focusing on navigation, forms, and documents.
  4. Schedule recurring reviews and assign ownership to a department or vendor.
  5. Provide a clear reporting channel for users to request alternate formats or report barriers.

Key Takeaways

  • Begin with an audit and a measurable remediation plan.
  • Keep documented evidence of remediation and communications.

Help and Support / Resources

  1. [1] City of Raleigh - Digital Accessibility
  2. [2] Raleigh Code of Ordinances - Municode
  3. [3] City of Raleigh - Accessibility Contacts

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