Skip to content

Accessibility statement

Last updated: 11 November 2026

We want Solorva to be usable by as many people as possible, including people who use a keyboard, a screen reader, magnification or other assistive technology. This page says what we have done, how we checked it, and where we know we fall short.

Our target

We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is a target we work towards, not a certification: no independent audit of Solorva has been carried out, and we do not claim full conformance.

What this covers

The public website at solorva.com (home, about, contact, changelog, privacy, terms, the data processing addendum, the help centre at /support and this page), the sign-in and sign-up pages, and the signed-in app used to set up a brand, create content and manage the library.

Content you generate with Solorva — images, captions, carousels, decks — is yours to check before you publish it. We cannot guarantee that generated images carry meaningful alternative text or that generated colours meet contrast requirements.

Display settings

The Accessibility settings button, in the footer of every public page and in the top bar of the app, lets you choose a larger text size (112% or 125%), a high-contrast mode, reduced motion and underlined links. Your choices are kept in this browser only and are never sent to our servers. Solorva also follows your device's reduced-motion setting and its light or dark theme.

How it was tested

  • Automated checks with axe-core in a real Chromium browser, at desktop and 375 px phone widths, on the public pages, the signed-in app and the staff admin area, in light and dark mode. They run on every change in our continuous-integration pipeline and fail the build on any serious or critical issue.
  • Scripted keyboard-only checks in a real browser, also on every change: Tab moving through the controls in page order with a visible focus indicator, a skip-to-content link, menus and dialogs that take focus, keep it while open and give it back, toasts and form errors in live regions, no sideways scrolling at 320 px wide or with text at 200%, and reduced motion respected.
  • Windows High Contrast (forced colours), emulated in Chromium on every change: a visible focus outline on every control, form fields that keep their edges, and icons that carry meaning have a text alternative.
  • Browser zoom at 200% and 400%, emulated in Chromium on every change: signing in, the menu, Create, Library, Settings and the other main pages keep all their content and controls on screen and usable.
  • The same public and signed-in keyboard and axe checks run by hand, before releases that change layout or focus, in Firefox and in WebKit (the engine behind Safari, run on Windows rather than on a Mac or iPhone).
  • Visual checks at 375 px for content that would otherwise need horizontal scrolling.

Known limitations

  • No person using a screen reader (NVDA, JAWS or VoiceOver) has yet tested Solorva end to end, and no pass on real phones and tablets has been done. Both are planned; until then this statement rests on automated and keyboard testing only.
  • Zoom and High Contrast have been checked by emulation in a test browser, not yet by a person using a real High Contrast theme or zooming a real browser, and Safari itself has not been tested on a Mac, iPhone or iPad.
  • Automated tools find only part of the issues that matter. They cannot judge whether a label makes sense or whether a journey is comfortable to complete.
  • The deck editor uses a fixed 16:9 canvas and is designed for larger screens. It works on a phone but is not comfortable there.
  • Images and text generated by AI models may not meet WCAG on their own; please review them before publishing.

Tell us about a problem

If something on Solorva is hard or impossible for you to use, please tell us through the contact page or, if you have an account, from Support in the app. Say which page and what happened, and what device and assistive technology you use if you are comfortable sharing it. We read every report and treat accessibility problems as bugs.