Public reports › School districts · North Carolina
School district · North Carolina · 4,405 students
asheboro.k12.nc.us · homepage scanned Oct 15, 2026 · WCAG 2.2 A/AA automated check
Accessibility score
36/100 · Failing
The homepage has critical barriers: content screen readers cannot describe, controls keyboards cannot reach, or text that cannot be read at normal contrast. This is the profile that draws complaints.
2
Critical
4
Major
0
Minor
Homepage as loaded by our crawler on Oct 15, 2026.
In plain English
The scan found significant issues that may hinder access for visitors with disabilities. This could affect people using screen readers or keyboard-only navigation, who may encounter problems navigating or understanding content. To improve accessibility, start by addressing the critical issues, such as fixing invalid ARIA attributes and ensuring interactive controls are properly structured. Note that automated scans don't catch everything, so further review is needed to ensure equal access under ADA Title II.
Findings
Each item is one failing rule; the count shows how many elements on the page trigger it. Severity follows axe-core impact levels.
ARIA attributes are used where they aren't allowed, which can make screen readers announce wrong information.
Who it affects
Blocks a task outright for some visitors (for example an image-only flyer with no text, or a form field with no label).
First fix
Remove or correct the attribute; often caused by a plugin or theme.
A menu/tab/list widget is incomplete, so assistive technology can't operate it.
Who it affects
Blocks a task outright for some visitors (for example an image-only flyer with no text, or a form field with no label).
First fix
Fix the widget markup or update the plugin that generates it.
Keyboard users land on elements that screen readers say don't exist.
Who it affects
Makes a task significantly harder (low contrast, links with no name, missing frame titles).
First fix
Remove tabindex from hidden elements or don't hide focusable content with aria-hidden.
A button inside a link (or similar) can't be reliably operated.
Who it affects
Makes a task significantly harder (low contrast, links with no name, missing frame titles).
First fix
Un-nest the controls; a card should have one link, not a link wrapping buttons.
Ensure every ARIA input field has an accessible name
Who it affects
Makes a task significantly harder (low contrast, links with no name, missing frame titles).
First fix
Follow the guidance in the linked Deque rule page.
Small links and buttons are hard to tap for people with motor impairments.
Who it affects
Makes a task significantly harder (low contrast, links with no name, missing frame titles).
First fix
Make clickable targets at least 24×24 CSS pixels or add spacing.
Severity guide
Blocks a task outright for some visitors (for example an image-only flyer with no text, or a form field with no label).
Makes a task significantly harder (low contrast, links with no name, missing frame titles).
Reduces clarity or consistency (heading order, landmarks, touch-target size).