Accessibility Statement

trybaeloop aims to follow recognized accessibility best practices and improve continuously. This is a commitment to practical work, not a claim of formal WCAG certification or a completed third-party audit.

We want public information and core interactions to be understandable across devices, input methods, and assistive technologies.

Public pages use semantic landmarks, a primary page heading, logical section headings, lists, and labeled navigation. Meaningful images receive contextual alt text, while decorative graphics are hidden from assistive technology.

We prefer native links, buttons, details elements, labels, and form controls before adding ARIA.

Public links, buttons, FAQ disclosures, and controls are intended to work without a mouse. Visible focus indicators identify where interaction will occur, and the homepage includes a skip link.

Controls should follow a logical source order and avoid clickable non-semantic containers. Complex app experiences remain under ongoing review.

Public authentication and verification forms use visible labels, suitable input types, autocomplete hints where appropriate, disabled states, and readable validation messages. Errors should not rely on color alone.

The design uses strong borders, readable type, responsive layouts, and high-contrast combinations. Content reflows for common mobile and desktop widths with usable touch targets.

Public pages respect reduced-motion preferences by minimizing non-essential animation and smooth scrolling.

AI media, third-party widgets, complex chat experiences, and fast-moving features can introduce gaps. Automated checks do not replace keyboard, screen-reader, zoom, contrast, and user testing.

We plan to keep auditing alt text, labels, heading order, dialogs, focus handling, media alternatives, and new feature flows.

If you encounter a barrier, contact support@trybaeloop.com with the page or feature, what you were trying to do, and a description. You may include browser or assistive-technology details if comfortable.

The operator must replace the placeholder address with a monitored email before launch. Reports will help prioritize fixes.