Accessibility
We aim at WCAG 2.1 AA. This page says what that means in practice here, and what we have not finished: a statement with no known gaps in it is usually a statement nobody checked.
What is in place
- Every interactive control is reachable and operable by keyboard, with a visible focus ring
- One
h1per page and a heading order that does not skip levels - Text alternatives on meaningful images; decorative images are marked as such so screen readers skip them
- Form fields have real labels, and errors are announced rather than only coloured
- Colour is never the only way information is conveyed: statuses carry text as well
- Layouts work from 320px upward, and text reflows to 200% zoom without horizontal scrolling
- All motion is disabled when a device requests reduced motion
- Body text meets AA contrast against its background
Known gaps
Some case-study imagery on BrandOS carries generic alternative text rather than a description of the work shown. PDF documents we distribute have not been audited for screen-reader structure.
Tell us
If something here blocks you, email info@turtlelabs.co.in with the page and what happened. We treat access barriers as defects, not feature requests, and will reply within 30 days.