Skip to content

Accessibility statement

Elara One aims to meet WCAG 2.2 at level AA on this website. What we do, what we know is not right yet, and how to tell us.

Last reviewed

In short

We want everyone to be able to use elaraone.app, including people who use a keyboard, a screen reader, magnification or voice control. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

We have not had an independent audit yet. If something gets in your way, email [email protected] and we will help, and fix it.

Our target

This statement covers the Elara One website at elaraone.app, including its documentation. We aim to meet WCAG 2.2 (opens in a new tab) at level AA, the standard UK public bodies are held to, even though the law only requires it of them.

The store admin and the starter storefronts are covered by their own accessibility work. A store's own website is the responsibility of the business that runs it.

What we do

  • Keyboard first. Every link, menu, tab and form can be reached and used with a keyboard, with a visible focus outline. A "Skip to content" link is the first thing on every page.
  • Structure you can navigate. Pages use landmarks and one main heading, with headings in order, so screen reader users can jump around.
  • Contrast in both themes. Text and controls are checked against WCAG contrast ratios in the dark and the light theme. You can switch theme at the foot of any page.
  • Less motion when you ask for it. If your device is set to reduce motion, animations are switched off.
  • Text that reflows. Pages are built to reflow on small screens and when zoomed, without scrolling sideways.
  • Illustrations described in words. Our product pictures are drawn in HTML. Each one is either described for screen readers or hidden from them because the text beside it says the same thing.
  • Forms that explain themselves. Every field has a visible label, errors say what went wrong and how to fix it, and nothing times out while you type.

Known limitations

We know about these problems and are working on them.

  • The admin video tour on the demo page may not have captions and a transcript when it is first published. We will add both.
  • Code examples in the documentation use syntax colours that may not all meet contrast ratios on their own. The code itself is always readable as plain text.
  • Spam protection on our forms uses Cloudflare Turnstile. Most people never see a challenge; if you are shown one and cannot complete it, email us instead.
  • Payment pages are provided by Stripe, and their accessibility is in Stripe’s hands.

How we test

We check pages with automated tools as we build them, and test by hand with a keyboard, with VoiceOver on macOS and iOS, and with NVDA on Windows, at narrow widths and high zoom, in both themes.

We plan an independent audit against WCAG 2.2 AA and will publish what it finds here.

Feedback and contact

If you find a problem, or need something from this website in a different format, tell us. Please say which page you were on and what happened.

Email
[email protected]
Post
Elara Labs Ltd, 128 City Road, London, United Kingdom, EC1V 2NX
Reply
We aim to reply within five working days.

If you are not happy with our response, you can contact the Equality Advisory and Support Service (opens in a new tab) (EASS).

About this statement

We prepared this statement on 24 October 2026, from our own testing. We review it whenever the website changes in a way that could affect accessibility, and at least once a year.