Accessibility

Accessibility statement.

We want Atlas to work for everyone who uses it. This page says what we aim for, what we tested, what is still wrong and how to tell us. Last tested 2026-10-05.

Report a barrier Security

Where we are

A target, a test and what it did not cover. We state the standard we work toward, not a compliance claim.

Target

WCAG 2.1 level AA

For the public website and the documentation. We do not claim conformance yet: the known issues below are open.

Automated test

axe-core, 2026-10-05

WCAG 2.0 and 2.1 A and AA rules on the landing page, plans, both product pages, sign-in, registration, security, status, the legal pages and the documentation, at 1440 and 390 px wide.

Not tested yet

People and assistive technology

No screen reader testing (NVDA, VoiceOver, TalkBack), no keyboard-only walkthrough of the dashboard, and the signed-in dashboard, account area and checkout were outside the automated run. Automated tools find only part of the problems.

What is in place

What the test and our build rules cover. Only what we have checked is listed.

Forms

Labelled fields

Sign-in and registration fields carry visible labels. The test found no missing labels on either page.

Phones

No sideways scroll

We check pages at 390 and 1440 px wide for horizontal scrolling, and controls on phones are built at least 40 px tall.

Motion

Reduced motion

Animated backgrounds and scroll effects are written to stop under the reduced-motion setting of your system.

Contrast

Fixed on 2026-10-05

The primary button, small grey text and in-text links were below the AA ratio and were corrected the day we tested.

Known issues

What is still wrong. Found by the same test. We list them so you do not have to find them.

Step numbers

Low contrast

The large step numerals on the landing page and on both product pages are dim (about 1.7 to 1) until you scroll to them, then they brighten.

Scrolling blocks

No keyboard access

Code samples, the plan cards on phones and a few tables scroll sideways, and a keyboard cannot reach them. Affects the landing page, plans, the Obfuscator page and the documentation.

Tell us

Hit a barrier? Write to us. Say which page, what you were trying to do and what you were using, such as a screen reader or keyboard only. We aim to reply within 5 business days and to fix what stops you from using Atlas.

Accessibility statement.

A target, a test and what it did not cover. We state the standard we work toward, not a compliance claim.

What the test and our build rules cover. Only what we have checked is listed.

What is still wrong. Found by the same test. We list them so you do not have to find them.

Hit a barrier? Write to us. Say which page, what you were trying to do and what you were using, such as a screen reader or keyboard only. We aim to reply within 5 business days and to fix what stops you from using Atlas.

Tell us where it breaks.