01 · Our approach
Make the platform work for more people, from the beginning.
People interact with software in different ways. Some enlarge text, navigate entirely by keyboard, use a screen reader, increase contrast or reduce movement. Others benefit from clearer spacing, simpler typography and information that does not depend on colour alone.
We are building those needs into Ariadnah’s shared interface and component system. When we improve a common control, navigation pattern, status indicator or data visualisation, that improvement can benefit every part of the platform that uses it.
Our ambition is for accessibility to be treated as an ordinary product requirement: designed, tested and reviewed whenever the platform changes.
02 · In the current platform
Accessibility options that can be combined.
Ariadnah includes accessibility preferences that people can combine according to their needs. The choices are saved on the device and work across the application.
Interface text and controls can be enlarged to 125%, 150% or 200%. At larger sizes, the application reorganises its navigation and layout to preserve usable reading space.
A reading-comfort option uses a simple system typeface with additional space between letters, words and lines.
Enhanced contrast strengthens text, controls, borders and focus indicators in both light and dark themes.
Reduced motion removes or shortens non-essential animation and avoids animated position changes.
Ariadnah also follows supported device and browser preferences for increased contrast, reduced motion and forced-colour presentation.
Beyond display preferences
Information should remain understandable however it is perceived.
Shared Ariadnah controls are built and tested with keyboard use and accessible naming in mind. Navigation, regions, forms and status messages use structured semantics intended to support assistive technologies.
Important status information does not rely on colour alone. Labels, symbols and text communicate meaning alongside colour. Key data visualisations include textual descriptions so their information is not available only as a graphic.
These foundations cover a growing part of the platform. They do not, by themselves, establish complete accessibility conformance across every page and workflow.
03 · What guides us
Established standards, applied to a developing platform.
Our current target is the Web Content Accessibility Guidelines 2.2 at Level AA across Ariadnah’s core customer workflows.
We also follow developments in the European accessibility framework, including EN 301 549 and the European Accessibility Act. These references help shape our approach; their inclusion here is not a claim that every formal requirement applies to, or has already been satisfied by, every Ariadnah service.
References to the European Accessibility Act describe what guides our work. They are not a claim that Ariadnah has completed a formal assessment of the Act’s applicability or demonstrated conformity under that legislation.
04 · Where we are today
Strong foundations, with validation still underway.
Ariadnah has a governed accessibility layer, user-controlled display preferences and automated tests for important shared interactions, contrast rules and presentation behaviour.
We are working toward WCAG 2.2 Level AA across core workflows. We do not yet claim complete product-wide conformance.
Complete conformance requires every relevant page and every step of a workflow to be evaluated. We are continuing that work through automated checks, manual keyboard testing, assistive-technology testing and feedback from people using the platform.
05 · What we are still improving
An accessibility page should also say what is not finished.
Some complex workflows and data-dense screens still require complete validation across representative screen readers, browsers and zoom combinations.
We are improving direct keyboard bypass navigation, including skip-to-content links. At the largest text setting, floating interface controls may occasionally overlap nearby information; the information remains available by scrolling, but the presentation should be better.
We will update this page as those limitations are resolved and as the scope of completed testing grows.
06 · Tell us what does not work
Accessibility problems are product problems.
If something prevents you from reading information, navigating the application or completing a task, please tell us. Include the page or workflow, what you were trying to do, and the browser or assistive technology you were using when possible.
We will acknowledge accessibility reports within two business days and provide an update after we have assessed the issue.
07 · Work with us
Accessibility improves through use, not statements alone.
Ariadnah is still evolving. We welcome conversations with customers, accessibility specialists and people with disabilities who can help us test real compliance work, not only isolated interface components.