Plattformsdokumentation

Accessibility commitment

Last updated: 20 July 2026. Saint Financial Group Limited is committed to making Elevale accessible to people with disabilities. This page explains our approach, the standards we meet, and how to report barriers you encounter.

This commitment covers the Elevale web application and the elevale.com marketing website. The platform is operated by Saint Financial Group Limited (Elevale) on our behalf.

Our standard

The Elevale web application conforms to WCAG 2.1 Level AA. Where practical, we also apply Level AAA guidance, including support for reduced motion preferences, enhanced colour contrast on key UI elements, and clearer focus indicators.

We apply the same accessibility standard to elevale.com and work to resolve barriers reported on public pages.

Accessibility is an ongoing effort. New features are designed with inclusive defaults, and we review existing areas as we ship updates.

What we do

Keyboard access

  • Core workflows are operable with keyboard alone, including navigation, forms, dialogs, and primary actions
  • Visible focus indicators show where you are in the interface
  • Keyboard traps are avoided in modals and overlays

Screen readers and semantics

  • Pages use semantic HTML landmarks, headings, and labels
  • Interactive controls have accessible names; icons and buttons are not conveyed by colour alone
  • Status changes and errors are announced where assistive technology needs them
  • Decorative visuals (for example the Otto voice orb) are paired with text alternatives and do not rely on animation alone

Visual design

  • Text and interactive elements target WCAG 2.1 AA contrast ratios; higher contrast is used on critical UI where feasible
  • Text can be resized and reflowed without loss of content or function up to 200%
  • Information is not conveyed by colour alone

Motion and media

  • When users set prefers-reduced-motion, non-essential animation is reduced or replaced with calmer alternatives
  • Autoplaying media with sound is avoided; users control playback where audio or video is present

Forms and errors

  • Form fields have visible labels and programmatic associations
  • Validation errors are described in text and linked to the relevant field
  • Required fields and input purpose are indicated accessibly where supported

Documents and content you create

You can improve accessibility in your own workspace content: use heading structure in wiki pages, add alt text to meaningful images, and avoid pasting text into images when plain text will do.

Assistive technology

Elevale is tested with current versions of major desktop browsers (Chrome, Firefox, Safari, Edge) and common assistive technology pairings, including NVDA and VoiceOver. Mobile browsers on iOS and Android are supported for core tasks.

We cannot guarantee compatibility with every browser, assistive technology, or configuration. If something does not work for you, please tell us using the contact details below.

Known limitations

Some areas outside the core application may have limitations, including:

  • Third-party embeds or integrations that we do not fully control
  • User-uploaded files and rich content in wiki or chat where quality depends on authors

We maintain an internal backlog of accessibility issues and prioritise fixes that block core tasks or affect many users.

Feedback and remediation

If you encounter a barrier, or need information in an alternative format, contact us via contact form. Please include:

  • The page or feature affected
  • What you were trying to do
  • Your browser and assistive technology (if relevant)

We aim to acknowledge accessibility reports within five business days and to provide a remediation plan or workaround for verified issues.

Continuous improvement

  • Design and engineering: Accessibility criteria are part of design review and code review for new work
  • Automated checks: Linting and scanning help catch common issues before release
  • Manual testing: Keyboard-only and screen reader spot checks on high-traffic flows
  • Training: Product and engineering teams receive guidance on inclusive patterns as standards evolve

We will update this page when our practices or conformance level changes materially.

Related documents