AtlasAccessibility

Accessibility

Version 2, last updated: 8 November 2026

Atlas aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the standard the European Accessibility Act points to through EN 301 549. Atlas partially meets it: most of Atlas does, and the parts that do not yet are listed below. This statement covers Atlas on the web. The Atlas app on your phone shows the same screens.

What is built in

  • A Skip to main content link is the first stop in the signed-in app. When you open another screen, a screen reader announces its heading once the screen has loaded.
  • Every form field has a name a screen reader can read. The build fails if a new field has none.
  • The priority buttons and the theme picker say which choice is selected.
  • Calendar events in the month grid, and the blocks in the day and week views, are buttons. Tab reaches them and Enter or Space opens them.
  • On and off settings are real switches that Tab reaches and Space flips.
  • The control that has keyboard focus is outlined, and the outline stands out from what is around it in every colour theme Atlas offers.
  • Atlas offers nine colour themes, including a High contrast theme. In each of them, text meets the contrast WCAG asks for on every screen we test.
  • In Profile, under Display and accessibility, you can choose larger text, bold text, high contrast, reduced motion and a simplified layout. They apply on every page, whatever the theme.
  • Atlas can be used in English, Arabic (right to left), French, Spanish and Japanese.

How we check

Automated checks run on every build. One fails the build when a form field has no name. Others test the skip link, the screen reader announcements, the on and off switches, the selected choices, the calendar buttons and the colours of each theme. We also run the axe accessibility engine in a real browser over every screen and dialog a trial user can reach, in every colour theme, at desktop and phone widths. The last full run was on 8 November 2026.

Known gaps

  • 66 text fields are named only by their example text. A screen reader reads it, but it disappears from the screen once you type. Every field we found like this on the main screens of the trial now has a proper name, and we are working through the rest.
  • You can move a calendar item by dragging it. To change its date or time without dragging, open the item and edit it in the form.
  • Voice is optional. Atlas can be used by tapping and typing.
  • Two colour themes, Calm and Paper, are not offered for now, because some of their text was too faint to read. If you chose one of them, Atlas shows you the nearest theme instead, Aurora or Folio, and keeps your choice for when the theme comes back.

What we have not tested yet

We have not yet tested Atlas from start to finish with a screen reader (VoiceOver, TalkBack, NVDA or JAWS) or with voice control, and Atlas has not had an outside accessibility audit. Automated checks find many problems, but not all of them.

Tell us if something does not work for you

If you cannot use part of Atlas, write to us. Say what you were trying to do and what got in the way. We aim to reply within 10 working days. If you need something from Atlas in another format, for example our legal texts as plain text, ask and we will send it.

support@atlaspa.app

If you are not happy with our reply

In the UK, the Equality Advisory and Support Service can advise you about your rights. In the European Union, each country has a body that enforces the European Accessibility Act, and you can contact the one where you live.

About this statement

The Atlas team at Rocksofttech wrote this statement from its own testing. It is reviewed whenever Atlas changes in a way that affects accessibility.