Accessibility statement
Last updated 27 April 2026. Our accessibility commitment for Glean.
Glean aims to meet WCAG 2.2 Level AA for perceivable, operable, understandable, and robust experiences across core flows (sign-in, add entry, timeline, dashboard, settings). This statement describes our target, how we assess compliance, and how to report issues.
Conformance target
We design and test against WCAG 2.2 AA criteria for key user journeys. Because the product evolves, full formal certification may lag individual releases; when gaps are identified, we prioritise fixes that unblock real users.
Assessment
This statement was last reviewed on 27 April 2026 via internal self-assessment against WCAG 2.2 AA. Reviews combine manual keyboard and screen-reader walkthroughs with automated checks in development. We have not yet commissioned a third-party audit.
Measures we take
We use semantic HTML where possible, keyboard-accessible controls (including shadcn / Base UI primitives), visible focus styles, and meaningful labels on interactive elements. Colour contrast follows the palette defined in our theme; charts and dense dashboards are reviewed for readability.
Known limitations
Complex data visualisations and user-uploaded images without alternative text may present residual barriers. We do not currently embed third-party maps or interactive embeds. The vision-assisted capture flow relies on camera and file inputs provided by the browser or operating system.
Feedback and contact
If you cannot complete a task due to an accessibility barrier, contact us at hello@glean.fit with the page URL, browser, and assistive technology if applicable. We aim to acknowledge reports within 5 working days and to share a remediation plan or fix timeline within 15 working days.
Related policies: Privacy Policy, Terms of Service.