Public reports › Special districts · Illinois
Special district · Illinois · population 26,000
bataviaparks.org · homepage scanned Oct 15, 2026 · WCAG 2.2 A/AA automated check
Accessibility score
42/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
2
Major
1
Minor
Homepage as loaded by our crawler on Oct 15, 2026.
In plain English
The scan found issues that may cause problems for visitors with disabilities, such as screen reader users or those who navigate with keyboards. For example, some content may not be read correctly or interactive controls may be hard to use. To improve accessibility, start by fixing the critical issues, like ensuring ARIA roles are used correctly. Automated scans like this one catch many problems, but not all, so further review is needed.
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.
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.
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).