Accessibility Statement
Last updated: April 24, 2026
Our Commitment
Studio Lybrand is committed to making Wanderhold usable by as many people as possible, including users with disabilities. We aim to provide an inclusive, equitable experience that complies with applicable accessibility laws in the regions where we operate.
Conformance Target
Wanderhold targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the technical standard referenced by Title III of the Americans with Disabilities Act (ADA) and by EN 301 549 under the European Accessibility Act (EAA). Where we are aware of gaps relative to that target, they are listed under “Known Limitations” below.
Measures We Take
- Accessibility is part of our design and code-review process for new features.
- We use semantic HTML and ARIA only where semantic HTML is insufficient.
- The interface supports full keyboard navigation; visible focus styles are preserved.
- We use semantic markup and ARIA so that screen readers can interpret the interface, though we have not yet completed a formal screen-reader audit (see Known Limitations).
- Color combinations are checked for WCAG AA contrast ratios on text and interactive elements.
- We do not use automated accessibility “overlay” widgets, which the European Commission and most accessibility experts consider inadequate.
Known Limitations
We are aware of the following areas and are working to address them. Each is being tracked internally.
- Setup wizard focus management: some multi-step transitions do not yet move focus to the new step heading.
- Decorative SVG icons: a small number of icons still need explicit
aria-hidden="true"attributes. - Mobile screen-reader pass: the play screen has had a desktop-first review; a mobile-Safari/VoiceOver pass is in progress.
Compatibility
Wanderhold is designed to be compatible with the latest two major versions of Chrome, Edge, Firefox, and Safari, and with VoiceOver and NVDA screen readers. The site is built to remain functional with JavaScript enabled and assistive technology active. We do not guarantee support for legacy browsers (more than two years old).
Third-Party Content
Some parts of the experience rely on third parties (Stripe Checkout for payment, Supabase authentication flows, Google sign-in). We work to choose providers with strong accessibility track records, but we do not control the accessibility of their interfaces. If you encounter a barrier in a third-party component, let us know. We can often provide an alternative path.
Reporting Accessibility Issues
If you encounter an accessibility barrier or have a suggestion, please email [email protected]. We aim to acknowledge reports promptly and to provide a substantive response, including a remediation plan or an alternative way to access the affected functionality, as soon as we reasonably can.
Please include the page URL, what you were trying to do, the assistive technology and browser you were using, and a description of what happened.
Formal Complaints (EU)
If you are an EU consumer and we are unable to resolve an accessibility complaint, you may also report it to the enforcement authority designated by your member state under the European Accessibility Act.
Assessment
This statement reflects a self-assessment of conformance against WCAG 2.1 AA. The statement was last reviewed on the date shown at the top of this page and is reviewed at least annually.
Contact
Studio Lybrand · 5900 Balcones Drive, Ste 4000, Austin, TX 78731 · [email protected]
See also: Privacy Policy · Terms of Service · Safety Policy.