SiteBrace

All state guides » North Carolina Title II accessibility

North Carolina Title II accessibility: April 2026 deadline + NC PDPA + state IT policy

North Carolina public-entity websites face the federal DOJ Title II rule (April 2024) with its April 24, 2026 WCAG 2.1 Level AA deadline for entities serving 50,000 or more (April 24, 2027 for smaller entities and special-purpose districts). North Carolina adds two state-level layers. The North Carolina Persons with Disabilities Protection Act (G.S. Chapter 168A) prohibits disability discrimination in places of public accommodation and is enforced through the Civil Rights Division of the North Carolina Department of Administration. The North Carolina Department of Information Technology (NCDIT) maintains a state-IT accessibility policy that references WCAG conformance for state-agency systems. North Carolina does not have a damage-multiplier statute equivalent to California's Unruh Act; the PDPA provides actual damages and attorney's fees but no statutory multiplier.

Short answer: if your entity is a North Carolina state agency, county, municipality, school district (LEA), community college, university in the UNC System, library system, or special district, you are covered by DOJ Title II and must meet WCAG 2.1 Level AA on your website by April 24, 2026 (population 50,000+) or April 24, 2027 (smaller). The NC PDPA adds a state-law cause of action. NCDIT's state-agency IT policy applies to state agencies but not directly to local entities. Site Brace audits any North Carolina public entity for $149 flat. Try a free single-page check on your homepage first.

The federal Title II deadlines:

  • April 24, 2026: public entities serving populations of 50,000 or more.
  • April 24, 2027: public entities serving populations under 50,000, and all special-purpose districts regardless of population.

Both deadlines apply to website content and mobile apps. WCAG 2.1 Level AA is the named conformance standard. Source: 28 CFR Part 35, published in the Federal Register April 24, 2024.

The rules that apply in North Carolina

1. ADA Title II (federal)

The DOJ April 2024 final rule is the load-bearing requirement for North Carolina public entities. Coverage and deadlines as above. See the DOJ Title II primer for the federal-rule overview.

2. North Carolina Persons with Disabilities Protection Act (G.S. Chapter 168A)

The PDPA prohibits discrimination based on a person's disability in employment, public services, public accommodations, and housing. The Civil Rights Division of the North Carolina Department of Administration is the primary state enforcement venue. The PDPA provides for actual damages and attorney's fees but, unlike California's Unruh Act, does not stack a statutory-damage multiplier on top of federal recoveries. A North Carolina entity sued for website inaccessibility typically faces a federal Title II claim with an optional PDPA claim layered alongside.

3. NCDIT state-IT accessibility policy

The North Carolina Department of Information Technology, established by the General Assembly to consolidate state IT services, maintains accessibility policies and procurement standards for state-agency systems. NCDIT's accessibility policy references WCAG conformance and is enforced through procurement review and state-agency IT governance. The policy applies to state agencies and to entities receiving meaningful state IT support; it does not directly cover counties, municipalities, school districts, or special districts, which fall under the federal DOJ Title II rule for their own websites.

For most North Carolina public entities, the federal Title II rule and the PDPA are the load-bearing pieces. State agencies have the NCDIT policy on top. North Carolina does not stack a damage-multiplier layer the way California does.

Which North Carolina entities are covered

Coverage is broad:

  • All North Carolina state agencies
  • 100 counties
  • 552 incorporated municipalities (cities, towns, villages)
  • 115 Local Education Agencies (school districts) plus dozens of charter-school boards
  • 58 institutions in the North Carolina Community College System (NCCCS)
  • 17 institutions in the University of North Carolina System (UNC-Chapel Hill, NC State, UNC Charlotte, UNC Greensboro, ECU, App State, UNCG, UNCW, NCCU, FSU, ECSU, WCU, NC A&T, Western Carolina, plus the affiliated institutions)
  • Public library systems (organized by county or regional system)
  • Special districts: airport authorities, water and sewer districts, sanitary districts, public transit authorities (CATS, GoRaleigh, GoTriangle, GoDurham)

The federal population threshold determines which deadline applies. Mecklenburg County (1.13M), Wake County (1.18M), Guilford County (550K), Forsyth County (385K), Cumberland County (335K), Buncombe County (275K), and Durham County (340K) fall under April 24, 2026. The metros of Charlotte (875K), Raleigh (470K), Greensboro (300K), Durham (290K), Winston-Salem (250K), Fayetteville (210K), Cary (180K), Wilmington (125K), High Point (115K), and Asheville (95K) also fall under April 24, 2026 either through their own population or through county-level coverage. Smaller municipalities and rural counties have until April 24, 2027.

What we typically find on a North Carolina public-entity site

The municipal CMS ecosystem in North Carolina looks like the rest of the country. CivicPlus, Granicus, OpenCities, Revize, and Streamline serve a large share of NC counties and cities. Smaller towns frequently run on custom WordPress or older bespoke platforms; the larger metros (Charlotte, Raleigh) have in-house web teams that ship cleaner accessibility baselines.

Findingaxe-core ruleTypical cause
Untagged PDFs (board agendas, RFPs, public-records requests, permit forms) Manual finding PDFs exported from Word without accessibility tagging
Color contrast on navigation, calls to action, and table cells color-contrast Vendor CMS template colors that fail 4.5:1
Form fields without labels on permit and public-records request forms label Custom form builders and vendor form tools that style placeholder text as label
Streaming-video board archives without captions Manual finding Live-streamed council and commission meetings posted without post-production captioning
aria-label on generic elements aria-prohibited-attr CMS theme customizations or overlay injection. See aria-label on a div.
Heading hierarchy mistakes on department and program pages heading-order CMS WYSIWYG editors that allow staff to skip heading levels
Document libraries with non-descriptive link text link-name Long lists of "Click here" or "Download" links rather than meaningful titles
NCDOT-style map embeds without keyboard alternatives Manual finding Public-works and transportation maps embedded as image-only or mouse-only interactive widgets

Notes on North Carolina's largest metros

Charlotte and Raleigh have invested in dedicated web teams that have iterated on accessibility for years. Recent city-level redesigns generally ship cleaner accessibility baselines than older county or town platforms. Department subsites within the cities (Charlotte Water, CATS Transit, Raleigh Parks, Wake County Public Health) often diverge from the citywide standard because they are owned by department staff with less web-accessibility coverage. The federal Title II rule applies to the city or county as a whole, including those department subsites. The Research Triangle area (Raleigh, Durham, Chapel Hill, Cary, Morrisville) has accumulated a particularly large web-content footprint between municipalities, the three UNC-System universities, and the regional transit and economic-development authorities.

Why overlays are a poor fit for North Carolina public entities

Accessibility overlays are heavily marketed to North Carolina municipalities and rural counties. We have written about why accessibility overlays do not actually make sites WCAG-compliant in detail. For North Carolina specifically: NCDIT's state-agency IT policy is a substantiation regime, and an overlay subscription does not substantiate. Local entities face the same Title II substantiation expectation. The FTC's April 2025 settlement with accessiBe makes overlay compliance claims a documented liability that NC county attorneys and city legal staff are tracking.

How Site Brace audits a North Carolina public-entity site

The standard page mix for a North Carolina public-entity audit:

  • Homepage
  • Department landing pages (top 4-6, varies by entity type)
  • Governing body page (City Council, County Commission, Board of Education, etc.)
  • Most-trafficked service pages (permits, utility billing, property tax, public-records requests)
  • Public meeting calendar
  • Document library or board-agenda archive
  • ADA accessibility statement (if one exists)
  • Privacy policy, contact

That mix covers up to 25 pages depending on the entity. The audit runs axe-core 4.10, captures element-level screenshots of every contrast failure, and packages findings into a written report with copy-paste fix code and 12 re-scans included over 12 months.

Pricing is $149 flat, one-time. To see what the report looks like, view a sample report we built for a fictional municipality.

Want to check your own site first? Run a free single-page check on your homepage or your most-trafficked service page - one URL, about a minute, no signup needed to see the result.

Start a North Carolina public-entity audit, $149

Related: