Trust

Accessibility

What we test, what that testing does and does not prove, and how to tell us when something blocks you.

Last reviewed August 2026

What we test

Automated accessibility checks run against this site in our continuous integration pipeline, alongside targeted tests for the things automation is bad at judging: keyboard focus order, visible focus indicators, interactive targets being large enough to hit, and the site remaining usable when motion is reduced or JavaScript does not run.

A failing check blocks the change from shipping. That is the mechanism we rely on rather than good intentions.

What that does not prove

This is not a conformance claim. Automated tools catch a minority of real accessibility problems, and we have not commissioned an independent audit or an assistive-technology user study. We are telling you what we do, not certifying an outcome.

Specific choices we have made

Content is legible without JavaScript rather than appearing only after an animation runs. Animation stops on its own instead of looping forever, and is disabled entirely when your system asks for reduced motion. Our spam protection uses a hidden form field that is hidden from screen readers too, so assistive technology users are not silently rejected for filling in a trap they could not see.

Tell us when we get it wrong

If something on this site blocks you, we want to hear about it, and we would rather hear about it than not know. Email chadi@peaklight.ai and describe what happened. We will also give you the information another way if that is what you need right now.

This page is being finalised. It states our current position honestly rather than waiting for legal polish. For the current version in writing, or for anything this page does not answer, contact us.