Keyboard-operable
The booking widget, the operator admin, and the customer portal can be driven by keyboard alone: focus is visible, order follows the page, and modals trap and restore focus.
Accessibility
Built to be used by everyone who fishes.
Our target is WCAG 2.2 AA across the widget, admin, portal, and this site. Here's what that means in practice today, and, just as plainly, what we're still working on.
01 The standard we build to
WCAG 2.2 AA, as a target, not a borrowed badge.
Baited aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the standard most accessibility law points to. We design and build against it; we don't claim a formal audit we haven't completed. The commitments below are specific things the product does today.
Screen-reader semantics
Native elements and ARIA labels carry the structure: form fields are labeled, status changes are announced, and decorative graphics are hidden from assistive tech.
Contrast from tokens
Text and interactive colors come from a shared token set audited for WCAG AA contrast, so the same checked values render across the widget, admin, portal, and this site.
Respects your settings
Motion honors prefers-reduced-motion, layouts reflow down to small screens without horizontal scroll, and touch targets are sized for a fingertip, not a cursor.
02 What's still in progress
We'd rather tell you where we're not finished than imply a clean bill of health.
- Automated checks are being wired into our build. We're adding automated accessibility testing to the pipeline so regressions get caught before they ship, alongside the manual keyboard and screen-reader passes we already run.
- No third-party audit yet. The product has not been through a formal external accessibility audit. When it has, we'll say so here, with the date and the standard, not a logo.
- The widget lives on operators' own sites. Our booking widget is built to be accessible, but the page it's embedded in is the operator's. We give operators an accessible component; the surrounding page is theirs to keep accessible too.
03 Report a barrier
Hit a wall? Tell us and we'll fix it.
If any part of Baited (the widget, the admin, the portal, or this site) is hard or impossible to use with your assistive technology, email us. Tell us the page, what you were trying to do, and the tool you were using (screen reader, voice control, keyboard, switch), and we'll treat it as a real bug.
We read every report and act on the genuine ones quickly. Accessibility barriers are defects, not feature requests.
hey@baited.devTry it yourself
Book a trip the way your anglers will.
Run the widget end to end, keyboard only, with a screen reader on. If something gets in your way, that's a report we want.