Raleigh WCAG Compliance for City Vendors

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

Raleigh, North Carolina requires city vendors and contractors to meet accessible digital content expectations when providing websites, apps, or digital services to the city. This guide summarizes the city procurement expectations, enforcement pathways, practical steps for suppliers, and where to find official vendor instructions so vendors can plan accessibility testing, remediation, and submissions.

Scope and Standards

The City expects digital content delivered under city contracts to follow established accessibility standards (commonly WCAG). The exact technical baseline and version may be set in individual solicitations or contract terms; consult procurement documents for each opportunity. For general vendor guidance and contact, see the City procurement page[1].

Check each solicitation for the specific WCAG version and conformance level required.

Penalties & Enforcement

The City handles accessibility expectations through procurement and contract compliance processes. Specific monetary fines, escalation amounts, and statutory penalties for WCAG noncompliance are not stated on the cited procurement page; vendors should rely on contract language for remedies and sanctions.[1]

  • Monetary fines: not specified on the cited page.
  • Escalation: not specified on the cited page; contracts typically describe cure periods and breach remedies.
  • Non-monetary sanctions: may include contract notices, requirements to remediate, withholding payments, termination for default, or debarment when set out in contract terms.
  • Enforcer: City Purchasing/Procurement Office handles contract compliance and initial complaints; use the procurement contact on official pages to report noncompliance.[1]
  • Appeals and reviews: protest, dispute, or cure procedures are generally governed by procurement rules and the contract; specific time limits are not specified on the cited procurement page.
  • Defences/discretion: contractors may rely on stated exemptions, existing legacy content schedules, approved variances, or documented reasonable accommodations when permitted by contract terms.
If a contract cites a remediation schedule, adhere strictly to deadlines to avoid contract remedies.

Applications & Forms

The City publishes vendor registration and solicitation response instructions through its Purchasing/Procurement office. The procurement page lists how to do business with the City but does not publish a single universal WCAG compliance form on that page; check individual solicitations or contact procurement for required attestations or test reports.[1]

Practical Compliance Steps for Vendors

  • Review contract and solicitation documents for explicit WCAG version and conformance level before bidding.
  • Perform automated and manual accessibility testing and prepare an accessibility conformance report.
  • Plan remediation timelines and include them in your project schedule and pricing.
  • Designate a point of contact for accessibility questions and for receiving notices from the City.
  • Include estimated costs for remediation and ongoing accessibility maintenance in proposals.
Maintain records of testing and remediation to demonstrate good-faith compliance.

Common Violations

  • Missing alternative text for informative images.
  • Poor keyboard navigation or focus order.
  • Insufficient color contrast for text and UI elements.
  • Forms and documents not accessible or not provided in accessible formats.

FAQ

What WCAG level does Raleigh require for vendors?
The required WCAG version and level are set in individual solicitations or contracts; the general procurement guidance page directs vendors to contract terms for technical baselines.[1]
Who enforces accessibility in contracts with the City?
Enforcement is managed by the City Purchasing/Procurement Office through contract compliance processes; contact information is available on the procurement page.[1]
How do I report an accessibility problem with a city contract deliverable?
Report issues to the procurement contact listed in the contract or solicitation; the procurement guidance page provides vendor contact pathways.[1]

How-To

  1. Read the solicitation and note any stated WCAG version and conformance level.
  2. Perform initial automated scans and manual sample testing on representative pages or features.
  3. Create an accessibility conformance report describing test methods, issues, and remediation plans.
  4. Submit required documentation with your proposal or to the contracting officer as directed.
  5. If notified of noncompliance, follow the remediation schedule in the contract and provide evidence of fixes.

Key Takeaways

  • Confirm WCAG requirements in each solicitation before bidding.
  • Keep test records and remediation evidence to support compliance.

Help and Support / Resources

  1. [1] City of Raleigh Purchasing / Doing Business with the City

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