Charlotte Vendor WCAG Rules for City Websites

Technology and Data North Carolina 3 Minutes Read · published February 06, 2026 Flag of North Carolina

In Charlotte, North Carolina, city contracts and vendor work that affect public-facing websites must meet accessibility expectations tied to WCAG standards and the city’s accessibility policy. This guide explains how Charlotte requires vendors to plan, test, and document WCAG compliance for city websites, who enforces those requirements, what penalties or remedies may apply, and practical steps vendors should follow when bidding, delivering, or updating site content or applications.

Scope & Applicable Standards

The City of Charlotte’s website accessibility policy establishes the obligation for city departments and their vendors to meet recognized accessibility standards such as WCAG (Web Content Accessibility Guidelines). Departments typically require evidence of conformance, remediation timelines, and accessible procurement language in contracts. Vendors should confirm the precise standard required in each solicitation and contract documents, and provide accessibility testing results and remediation commitments to the contracting officer[2].

Penalties & Enforcement

Charlotte’s published website accessibility policy and procurement terms set contractual obligations but do not list civil fine schedules on the accessibility policy page; specific monetary penalties for noncompliance are not specified on the cited page[1]. Enforcement is generally contractual: the city’s contracting office or the department issuing the solicitation enforces compliance, often through contract remedies, compliance orders, withholding payments, or requiring corrective action.

  • Fine amounts: not specified on the cited page; contractual remedies may apply[1].
  • Escalation: first notice, required remediation, and further contractual remedies for continuing breaches; exact escalation steps not specified on the cited policy page[1].
  • Non-monetary sanctions: correction orders, withheld payments, requirement to remediate or replace deliverables, and potential contract termination.
  • Enforcer & complaint path: Procurement/Contracting officer or the department’s accessibility coordinator handles complaints and compliance; official contact and procurement rules are published by the city[2].
  • Appeals & review: appeals typically follow contract dispute procedures in the solicitation or contract; time limits for notices or appeals are governed by contract terms and are not specified on the general accessibility page[1].
If a contract names remediation deadlines, follow them closely and document all remediation efforts.

Common violations and typical outcomes

  • Missing alternative text for images — requires remediation and retesting.
  • Poor keyboard navigation — corrective work and review.
  • Insufficient color contrast — documented fixes and validation.

Applications & Forms

The city does not publish a single universal "WCAG certification" form; solicitations often require specific deliverables such as a Voluntary Product Accessibility Template (VPAT) or test reports. If a solicitation requires a named form or submission process, that requirement appears in the solicitation or contract package; a universal form is not specified on the general accessibility policy page[1].

Provide a VPAT and recent accessibility test report when requested by procurement documents.

How-To

  1. Review the solicitation and contract accessibility clauses to confirm the required WCAG level, deliverables, and remediation timelines.
  2. Prepare or obtain a VPAT and an independent accessibility test report showing current compliance status and known issues.
  3. Remediate identified failures, prioritize high-impact barriers, and document fixes with screenshots and test results.
  4. Submit required deliverables to the contracting officer by the dates specified in the solicitation or contract.
  5. If a compliance dispute arises, follow the contract dispute and appeal procedures and maintain records of remediation actions and communications.

FAQ

Do Charlotte city contracts require WCAG conformance?
Many Charlotte solicitations include accessibility requirements and expect vendors to meet specified WCAG levels; check each solicitation for exact requirements.[2]
What evidence should a vendor provide?
Vendors are commonly asked to provide a VPAT, accessibility test reports, and a remediation plan when accessibility issues are found.
Who enforces accessibility for city websites?
Enforcement is handled through the contracting department and procurement office; complaints are routed to the department responsible for the contract.[2]

Key Takeaways

  • Check each solicitation for the exact WCAG level and deliverables required.
  • Provide a VPAT and test reports when requested, and document remediation steps.
  • Contact the contracting officer early if you identify accessibility issues that affect delivery timelines.

Help and Support / Resources

  1. [1] City of Charlotte Accessibility
  2. [2] City of Charlotte Procurement

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