Our target
BusyBi is working toward WCAG 2.2 Level AA for the public site and future member product. Accessibility is a release requirement, not a final polish step, but this pre-launch experience has not yet completed an independent conformance audit.
Design and engineering baseline
- Keyboard access, visible focus, meaningful landmarks, headings, labels, and status announcements.
- Readable contrast, zoom and reflow support, generous targets, and no meaning conveyed by color alone.
- Reduced-motion behavior and no essential interaction that depends only on hover, dragging, or a precise pointer.
- Text alternatives and captions where media conveys meaning.
- Accessible authentication, age-assurance, safety reporting, payments, and account recovery—including vendor-hosted steps.
Feedback and accommodation
If a page, form, or document creates a barrier, contact support with the page, task, assistive technology if you wish to share it, and the format or accommodation that would help. You do not need to disclose a diagnosis. Safety-critical and account-access barriers should receive priority.
Known launch work
BusyBi still needs representative assistive-technology testing, an independent audit, accessible vendor reviews, issue-response targets, and a published conformance statement before full member launch.
Use a discreet subject line.
Share only what is needed for us to route the request. Do not email passwords, payment-card details, identity documents, or intimate media.
[email protected]