Public reports › School districts · Colorado
School district · Colorado · 27,541 students
bvsd.org · homepage scanned Oct 16, 2026 · WCAG 2.2 A/AA automated check
Accessibility score
49/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.
1
Critical
5
Major
1
Minor
Homepage as loaded by our crawler on Oct 16, 2026.
In plain English
The scan of the BVSD website found several issues that may cause problems for visitors with disabilities. For example, some content may not be readable by screen readers or navigable using only a keyboard. To improve accessibility, it's a good idea to start by fixing the critical issue and addressing problems with hidden content and list construction. Automated scans like this one catch many issues, but not all, so further review is also recommended.
Findings
Each item is one failing rule; the count shows how many elements on the page trigger it. Severity follows axe-core impact levels.
Ensure elements with an ARIA role that require parent roles are contained by them
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
Follow the guidance in the linked Deque rule page.
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.
List structure is broken, so screen readers can't announce 'list of 5 items'.
Who it affects
Makes a task significantly harder (low contrast, links with no name, missing frame titles).
First fix
Only put <li> inside <ul>/<ol>; remove stray elements injected by the editor.
Ensure every ARIA button, link and menuitem 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.
Ensure that elements labelled through their content must have their visible text as part of their 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.
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.
Users can't pinch-zoom on phones to enlarge text.
Who it affects
Reduces clarity or consistency (heading order, landmarks, touch-target size).
First fix
Remove user-scalable=no and maximum-scale=1 from the viewport meta tag.
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).