Accessibility statement
SplashPadHub is built to be usable by every parent — including those navigating with a screen reader, keyboard only, switch device, or low vision. Here's what we commit to and what we know is still imperfect.
We target WCAG 2.1 Level AA. We audit every release for keyboard reachability, focus visibility, color contrast, semantic headings, and screen-reader landmarks. If something is broken for you, email accessibility@splashpadhub.com and we'll triage within 5 business days.
What we commit to
WCAG 2.1 AA target
We aim for Web Content Accessibility Guidelines (WCAG) 2.1 Level AA conformance across every public page. Every component is audited for color contrast, keyboard reachability, focus visibility, semantic landmarks, and alt text on meaningful imagery.
Keyboard navigation
All interactive elements (links, buttons, search dialog, filter chips, modals) are reachable and operable with keyboard alone. Focus order follows visual order. Skip links are present on every page header.
Screen-reader friendliness
Every page has a single h1, semantic headings descend logically, breadcrumbs use aria-label and aria-current, decorative emoji use aria-hidden, and form labels are explicit. The interactive map exposes pad names as accessible-named markers.
Reduced motion
We honor prefers-reduced-motion across all animated transitions. Hover effects collapse to instant state changes. Carousels and parallax are not used.
Color contrast
Text and interactive UI meet at least 4.5:1 against background in light mode and 4.5:1 in dark mode. Brand chips and badges are reaudited every release; the audit log lives in our public repo.
Plain language
Splash pad guidance is written for parents reading on a phone with a wet-handed kid. We use short sentences, no jargon, and lead with the answer. Every Q&A entry has a 30–60 word direct answer first, expanded context after.
Standards we measure against
- WCAG 2.1 Level AA — Web Content Accessibility Guidelines
- Section 508 (US federal) — to the extent applicable to a private directory
- EN 301 549 (EU) — for EU-based visitors
- ADA Title III principles — applied to public-facing digital services
Known limitations
Honesty is faster than discovery. These are the gaps we know about and are actively working to close.
- 1.User-submitted photos may not all carry author-supplied alt text. We backfill descriptions where possible and prompt submitters for context, but historic gaps exist.
- 2.The interactive splash pad map relies on a third-party tile layer and clustering library. Cluster counts are announced via marker text, but pan/zoom gestures are touch-first; keyboard-only pan/zoom relies on browser fallbacks.
- 3.Some embedded source PDFs in our reports section are linked through to original publishers; their accessibility is outside our control. We host plain-HTML summaries alongside every PDF link.
Report an accessibility issue
Last reviewed
This statement was last reviewed in the most recent release audit. The full a11y audit log lives in data/a11y-audit-2.md in our public repo. Audit cadence: monthly + after any major UI release.