ACCESSIBILITY

Accessibility

Last reviewed 17 August 2026

Where Clarus stands

Clarus aims to meet WCAG 2.1 Level AA. That is the standard referenced by the Americans with Disabilities Act in practice, by the European Accessibility Act through EN 301 549, and by the UK Equality Act's reasonable-adjustment duty.

This site is built and checked against it rather than declared compliant and left alone. Where something falls short it is listed below instead of being quietly omitted.

What works

• Keyboard only. Every link, button and form control is reachable and operable without a mouse, and the focus outline is never suppressed anywhere on the site.
• Skip to content. The first thing the keyboard reaches on any page jumps past the navigation.
• Screen readers. Pages have one main heading and a sensible heading order, every image carries alt text, and every form field has a name. The decorative product animations are marked as decorative so they are not read out as if they were controls.
• Motion. The site animates a lot. If your system asks for reduced motion, every animation on every page stops, including the 3D mark on the home page.
• Zoom and reflow. Nothing blocks pinch-zoom, and text can be enlarged to 200% without losing content.
• Colour. Body text and controls meet the AA contrast minimum, and no instruction anywhere depends on colour alone.

Known gaps

Two, and neither is fixed yet:

• The product animations on the home page are illustrations of the app. They are hidden from screen readers rather than described, because a narrated blow-by-blow of a fake email window would be noise. The same information is in the text beside every one of them.
• The Clarus application itself has not been through the same audit as this website. Work on it is ongoing, and it is not claimed to meet WCAG 2.1 AA today.

No accessibility overlay

Clarus does not use an accessibility overlay, widget or toolbar. Those are the buttons that promise to make a site compliant on the fly. They do not work, people who rely on assistive technology consistently ask sites not to use them, and in January 2025 the US Federal Trade Commission fined one vendor $1 million over what its product claimed to do.

Everything above is done in the HTML and CSS of the pages themselves.

If something blocks you

Email [email protected] with accessibility in the subject. Tell us the page and what happened, and roughly what you were using (a screen reader and its version, keyboard only, high contrast, heavy zoom) if you can.

Clarus is built by one person, so you will be talking to the developer rather than a queue. We aim to reply within five working days, and if a fix is going to take longer than that you will be told what it is and when.

If you need something on this site in another form (a document, a price, anything), ask and it will be sent to you directly.

This statement

Last reviewed 17 August 2026. It applies to getclarus.dev and its subpages.

It is based on a real audit rather than a template: automated checks across every page, contrast measured from the rendered stylesheet, and a keyboard pass. It will be updated when the site changes or when a gap above is closed.