Our accessibility commitment

Kid Activities Today is committed to making kid-friendly activity discovery accessible to every family, including people using assistive technology.

We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We build and test our own site against that standard, and we keep improving.

How to report an accessibility issue

If something on our site isn't working for you — a missing label, a keyboard trap, poor contrast, a screen-reader problem, or anything else — please let us know. We want to fix it.

Fastest path: use our feedback form and select "Bug report" or "Other" as the topic. Please include:

  • The page URL
  • What assistive technology you use (if any) — e.g. VoiceOver, NVDA, JAWS, screen magnifier, keyboard-only
  • What happened and what you expected

We read every submission. We aim to respond within 5 business days.

Report an issue

What we've done

Our current site includes:

  • Keyboard operability: every interactive element is reachable via Tab, with a visible focus indicator. The city picker supports arrow keys and Escape.
  • Skip-to-content link on every page for keyboard users.
  • Semantic HTML: proper landmarks (header, main, footer), headings, and form labels.
  • ARIA support: menus, dialogs, filters, and sliders expose state (pressed, expanded, current value) to screen readers.
  • Decorative icons are marked aria-hidden so screen readers don't read them.
  • Reduced motion: we respect prefers-reduced-motion and disable animations for users who prefer them off.
  • Color contrast: text meets WCAG AA contrast ratios.
  • Screen-reader live regions announce filter result counts and slider value changes.

Known limitations

We're open about what we're still working on:

  • In progress Manual screen-reader testing with VoiceOver / NVDA / JAWS across all core flows. We've done technical ARIA compliance but not full user testing.
  • In progress Full focus trap within the About dialog. The dialog uses aria-modal="true" and returns focus on close, but a user can Tab beyond the dialog boundary.
  • Not yet covered Third-party embeds (newsletter signup widget, analytics scripts) are outside our direct control. We've chosen providers that publish a11y commitments, but we can't guarantee their compliance.
  • Not yet covered Our internal admin tool (/admin.html) is not held to the same a11y bar. It's not intended for public use.
  • Not yet covered Some activity data pulled from partner APIs (descriptions, images) may not themselves be screen-reader optimized.

Technical standards

Target conformance: WCAG 2.1 Level AA.

Testing methodology:

  • Automated scanning with axe-core / WAVE (periodic)
  • Manual keyboard navigation testing on Chrome, Safari, Firefox
  • Mobile responsiveness testing on iOS and Android

Standards referenced: WCAG 2.1, Section 508 (US federal), and the Americans with Disabilities Act Title III (for public-facing services).

Continuous improvement

We review this page and our site's accessibility at least quarterly and whenever we ship a significant new feature. Issues reported to us are typically addressed within 30 days, depending on complexity.

If you have an urgent access need and can't use our site, please reach out via the feedback form and we'll do our best to provide the information you're looking for through another channel.

Last updated: April 18, 2026

← Back to activities