Butlr

← Home

Accessibility Statement

Last updated: 2026-05-12

Our commitment

Butlr is built to be usable by people with a wide range of disabilities — vision, hearing, motor, cognitive. We target conformance with WCAG 2.1 Level AA across every public-facing page. Where we fall short, we list it openly below and commit to specific fixes.

What's been built for accessibility

  • Semantic HTML: every page uses native form elements, headings (h1 → h3), and landmark regions (header / main / footer / nav).
  • Keyboard navigation: every interactive element is keyboard-accessible. Tab order follows visual order. No keyboard traps.
  • Screen-reader labels: every form field has an explicit <label>. Required fields use both visual indicator ("required") and aria-required. Hidden radio inputs are paired with clickable labels.
  • Focus indicators: every focusable element shows a 2px outline in the accent color (CSS :focus-visible).
  • Color contrast: text is rendered at WCAG AA contrast against the surface color in both light and dark modes.
  • No motion-required UX: nothing requires gesture or motion. The hero animations are decorative only and respect prefers-reduced-motion on Phase 2.
  • Dark mode: full theme toggle persisted in localStorage with anti-flash pre-render.
  • Touch targets: all interactive elements meet the 44px × 44px minimum on mobile.
  • No timed forms: the wizard has no session timeout. Step state persists in hidden inputs and survives back/forward navigation.

Known gaps

  • Reduced motion: the rotating wave animation in the hero does not yet check prefers-reduced-motion. Planned for Phase 2.
  • Screen-reader testing: we've tested with VoiceOver on macOS Safari but not yet with NVDA on Windows. NVDA pass-through targeted before public launch.
  • High-contrast mode: Windows High Contrast not yet explicitly tested.
  • Audio captions: the Phase 2 AI voice agent (when shipped) will offer real-time transcript in the user's pane.

Need help or found a problem?

If you can't use part of Butlr because of an accessibility barrier, email accessibility@butlr.ai with: the page URL, the browser + screen reader (if any), and a description of what didn't work. We aim to respond within 2 business days and fix the issue within 30 days for WCAG-AA-level barriers.

Alternate ways to use the service

If filling out the web wizard is not accessible to you for any reason, email hello@butlr.ai with the same information the form asks for (business name, business phone, the goal of the call, your callback number) and we will queue the call manually.