North Carolina local government websites: accessibility test results
Automated testing detected at least one failure against WCAG 2.1 Level A and AA success criteria on 29 of the 31 North Carolina local government websites tested (94%).
Scans run on October 20, 2026.
- Websites tested
- 31
- With at least one detected failure
- 29
- Median detected failures per website
- 51
- Pages tested
- 1,132
Most frequently detected success criteria
| Success criterion | Level | Websites with at least one failure |
|---|---|---|
| 4.1.2 Name, Role, Value | A | 22 (71%) |
| 1.4.3 Contrast (Minimum) | AA | 20 (65%) |
| 1.1.1 Non-text Content | A | 15 (48%) |
| 2.4.4 Link Purpose (In Context) | A | 12 (39%) |
| 2.5.3 Label in Name | A | 12 (39%) |
| 1.3.1 Info and Relationships | A | 9 (29%) |
| 1.4.1 Use of Color | A | 5 (16%) |
| 3.1.1 Language of Page | A | 4 (13%) |
| 1.4.4 Resize Text | AA | 1 (3%) |
| 2.1.1 Keyboard | A | 1 (3%) |
Dates in the DOJ Title II web rule
Of the websites tested, 8 belong to entities in the April 26, 2027 tier and 23 to entities in the April 26, 2028 tier.
Browse by county
- Alleghany County (1)
- Brunswick County (3)
- Columbus County (2)
- Forsyth County (2)
- Guilford County (2)
- Harnett County (1)
- Haywood County (2)
- Henderson County (1)
- Johnston County (1)
- Madison County (1)
- Mecklenburg County (1)
- Montgomery County (1)
- Pender County (1)
- Pitt County (3)
- Randolph County (1)
- Stanly County (1)
- Transylvania County (1)
- Union County (1)
- Wake County (3)
- Watauga County (1)
- Wayne County (1)
Scope and limitations
What this report is
This is an automated conformance test of publicly accessible pages on each listed entity's website, measured against the Web Content Accessibility Guidelines (WCAG) 2.1, Level A and Level AA success criteria. It was produced on October 20, 2026 using axe-core 4.14.0, testing 1,132 pages.
What this report is not
This report does not determine whether each listed entity satisfies any legal obligation. Legal determinations under the Americans with Disabilities Act or any other statute or regulation are for your legal counsel, not for an automated test, and nothing in this document should be read as a legal opinion or as advice.
Automated testing identifies a subset of accessibility barriers. Published estimates of automated coverage range from roughly 20% to 57% of issues depending on methodology and the site being tested. Categories of barrier that automated testing cannot reliably detect include, among others:
- whether alternative text is meaningful rather than merely present
- keyboard traps and illogical focus order
- whether content is usable and comprehensible with a screen reader
- accuracy and synchronization of captions and audio description
- accessibility of linked PDFs and other documents
- whether an accessible alternative conveys equivalent information
A site with zero findings in this report may still present significant barriers to users with disabilities. Manual testing and testing with assistive technology by people with disabilities are necessary to assess a site's actual usability, and no automated test substitutes for them.
No findings are a guarantee of anything. This report describes what an automated test detected on specific pages on a specific date. Website content changes continuously.