Accessibility statement

[01]

What we are aiming at

WCAG 2.2 Level AA, across the marketing site and the product. We are not claiming a completed audit against it. This page says what we build to, what we know is solid, and what is not done, because an accessibility statement that only lists successes is not useful to anybody deciding whether they can use the software.

[02]

How it is built

Accessibility comes from the component layer rather than from a pass at the end. A field wires its label, hint, error and description to the control it wraps, so a form gets most of what it owes a screen reader by being built out of the design system at all.

• Every control has a label, and an icon-only button carries an accessible name.
• Everything reachable by mouse is reachable by keyboard, in an order that matches the screen.
• Focus is always visible, drawn with a ring that does not shift the layout by a pixel.
• Overlays trap focus, close on Escape, and return focus to whatever opened them.
• State is never carried by color alone.
• Contrast is checked deliberately in both the light and the dark theme.

[03]

Motion

The site uses scroll-linked motion on the home page. Setting "reduce motion" in your operating system turns the pinned hero, the background video and the scroll reveals off, and the page renders as a static composition instead. That is a real alternative rather than a shortened animation.

[04]

Known gaps

Stated plainly, and each one is on the list:

• No independent accessibility audit has been completed. We test with keyboard and screen reader ourselves.
• Some dense operational tables are hard going at high zoom on a narrow window.
• Photographic bands on the marketing site carry decorative images with empty alt text; the meaning is always in the adjacent text, but a reader who wants the picture described will not get it.
• Documents you upload are yours, and we cannot guarantee the accessibility of a PDF we did not produce.

[05]

If something blocks you

Write to hello@alakili.com and describe what you were trying to do and what got in the way. Tell us the assistive technology and browser if you can. We treat a blocking accessibility bug as a production issue, not as a feature request.

If you need something in a different format to evaluate the product, ask and we will produce it.