Accessibility
Accessibility Statement
Hybrid aims to make the business operating system for independent workers usable across public pages, account flows, client-facing artifacts, checkout-related flows, and signed-in workspace features.
Effective Date
August 10, 2026
Accessibility is product quality
Hybrid aims to make core public, account, client-facing, and payment flows usable by people with disabilities.
WCAG is the working target
Our practical target is WCAG 2.2 AA where feasible for new and materially changed pages and screens.
Issues should be reported
Accessibility problems can be sent to support so we can reproduce, prioritize, and fix them.
Some areas are evolving
Hybrid is still changing quickly, so previews, third-party embeds, and older flows may need additional hardening.
Commitment
Hybrid is built for independent workers and their clients. Accessible product behavior is part of user trust, not a decorative add-on.
Hybrid aims to make public pages, account flows, legal pages, client-facing artifacts, checkout-related flows, and signed-in workspace features usable with assistive technology and keyboard navigation.
For new and materially changed pages and screens, Hybrid's practical target is WCAG 2.2 AA where feasible, while recognizing that third-party providers and embedded experiences may have separate accessibility controls and limitations.
Current Practices
Hybrid uses a mix of design-system rules, automated checks, and human testing to reduce accessibility regressions.
- Use semantic headings, labels, buttons, and links where possible.
- Preserve keyboard access for navigation, forms, dialogs, and core actions.
- Keep visible focus states, readable contrast, and responsive layouts in public and product pages.
- Prefer accessible reusable interface components and explicit aria labels for icon-only controls.
- Treat client-facing and payment paths as a high accessibility priority before broad launch.
Known Limits
Hybrid is still under active development, and some limitations may remain while features are being built or replaced.
- Some beta, preview, internal, or older product areas may need additional accessibility review before public launch.
- Third-party checkout, wallet, map, media, calendar, AI, or embedded provider features are governed by the provider's own accessibility implementation.
- Generated content, uploaded files, and user-authored client artifacts may not always be accessible unless the user formats them accessibly.
Contact
If something blocks access, send enough detail for Hybrid to reproduce and prioritize the issue.
Email support@hybrid.app with the page URL, browser/device, assistive technology if applicable, what you were trying to do, what failed, and any workaround you found.
Hybrid may ask for follow-up details so we can reproduce the issue. Accessibility feedback may be handled with support, product, engineering, or provider teams depending on the affected area.