ACCESSIBILITY
Usable, or it is a bug.
PLAIN-ENGLISH SUMMARY · FULL LEGAL TEXT PUBLISHES WITH LAUNCH
The standard we build to
WCAG 2.2 at Level AA. We treat that as the floor rather than the goal, because a back office you cannot operate is not a back office.
What that means in practice
Every interactive element reachable and operable by keyboard with a visible focus state, text that meets contrast requirements, real semantic structure rather than styled divs, and motion that respects a reduced-motion preference.
Where we are honest about the gap
Bizzle is pre-launch and has not yet been through an independent accessibility audit. We have built to the standard; we have not yet had anyone else verify it. We will publish what that audit finds rather than only the parts that flatter us.
Assistive technology
We test with keyboard navigation and screen readers. Coverage across every combination of browser and assistive technology is not complete, and reports of what breaks in yours are genuinely useful.
The phone matters here
For some people, a system that answers the phone, transcribes the call and files the outcome is more accessible than any interface. That is a large part of why the front desk exists.
Telling us something is broken
Email support@bizzle.ai with what you were trying to do and what stopped you. An accessibility barrier is treated as a defect, not a feature request, and we will tell you what we are doing about it.
This statement
It will be updated as the audit completes and as the product ships. Nothing here is a claim of full conformance, and we would rather say so than imply otherwise.