Usable by everyone.

We want Alide to work for people with disabilities, including people who use screen readers, magnification, speech input, switch devices, or a keyboard alone. We treat an accessibility barrier as a bug: it goes in the same queue as anything else that stops the product working, not a separate wish list.

Our target is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That standard is the benchmark commonly referenced in relation to the Americans with Disabilities Act (ADA) and Section 508.

Partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the product meets the standard, and some parts have not been fully verified. We are saying that plainly rather than claiming full conformance, because we have not yet completed an independent third-party audit. When we do, this page will say so and give the date.

What is implemented and in the product today:

• A visible "Skip to content" link on every page.
• Visible keyboard focus indicators throughout the site and the extension rail. Every interactive control can be reached and operated with a keyboard alone.
• Full support for prefers-reduced-motion: if your system asks for reduced motion, animations and transitions are switched off rather than merely shortened.
• Semantic landmarks, real buttons and headings, and ARIA labelling on controls whose purpose is not carried by their visible text.
• Light and dark themes, both designed against WCAG AA contrast ratios, with a theme control that reports its own state.
• Status changes in the rail, including score, review progress, and errors, are conveyed in text, not by colour alone.
• Content is readable and operable at 200% zoom and on small viewports.

We would rather name these than let you discover them:

• Host pages we do not control. The browser extension renders alongside third-party sites such as claude.ai and chatgpt.com. We are responsible for Alide's own interface; we cannot fix accessibility issues in the pages it sits next to.
• No completed third-party audit. Our testing to date is internal, and internal testing reliably misses things. An external review is planned.
• Screen-reader coverage is uneven. The rail updates live as you type, and we are still improving how those updates are announced so they are informative without being noisy.
• The desktop app attaches to other applications. It reads and writes the prompt field of whatever app you point it at, so parts of that experience depend on the accessibility of that other application.
• Rendered mathematics. Math shown in the rail is rendered visually; screen-reader announcement of complex expressions is not yet where we want it.

This is the part we most want you to use. If any part of Alide is difficult or impossible to use, email alideteam@gmail.com with "Accessibility" in the subject.

It helps if you can tell us the page or screen, what you were trying to do, and the assistive technology, browser and operating system you were using, but please write to us even if you cannot supply all of that.

What we commit to: we aim to acknowledge every accessibility report within 5 business days, tell you what we intend to do about it, and give you a way to get the information or complete the task in the meantime if a fix will take time. A founder reads this inbox directly.

If our response does not resolve the problem, say so in reply and ask for it to be escalated; we will treat that as a formal complaint and respond in writing.

If you cannot complete something in Alide because of an accessibility barrier, contact us and we will provide the information or carry out the task with you by email while the underlying issue is fixed.

This statement is reviewed when the interface changes meaningfully and at least twice a year. It describes the Alide website, the browser extension, and the desktop applications. It was last reviewed on July 30, 2026, based on internal testing.

Accessibility is not a state we reach and stop. If this page ever describes the product more favourably than your actual experience of it, that gap is the bug. Please tell us.