Accessibility in the private beta
Accessibility.
We are working toward the WCAG 2.2 Level AA accessibility standard. Testing is still in progress during our private beta, and we have not completed an independent accessibility audit.
Keyboard and focus
Our goal is to make Biyra usable with a keyboard, with a clear focus indicator and predictable navigation.
Readable and adaptable
We aim for readable text, clear headings, and layouts that work when you zoom in. Information should not depend on color alone.
Motion under your control
The landing-page background video is muted. If your device is set to reduce motion, it shows a still image instead.
01 / Target
The standard we are working toward.
The current acceptance criteria cover keyboard use, focus behavior, labels and errors, media controls, reduced motion, contrast, and layouts at 200 percent zoom. WCAG 2.2 Level AA is the target for implemented customer flows.
02 / Verification
Verification is still in progress.
Biyra has not completed an independent accessibility audit or certification, and this page does not claim universal conformance. Accessibility review remains part of our beta work as supported flows are completed.
03 / Boundaries
Current limitations.
The product currently uses one light visual palette and does not offer a theme switch. Browser, device, and assistive-technology combinations have not been exhaustively verified. Some connected services may have their own accessibility features when you use them.
04 / Reporting
Report an accessibility barrier.
Tell us the route or task, what you expected, what happened, your browser and device, and any assistive technology involved. Do not send passwords, cookies, recovery codes, or private property media in the report.
Tell us what stopped you.
Use the contact form so our team can follow up without exposing account or project details.