Accessibility

General information and accessibility statement for the onelife.com website

OneLife is committed to making its websites accessible so that as many users as possible can access its content and services.

To achieve the best possible result, accessibility is taken into account by all teams (functional and graphic design, development, content creation, etc.) throughout the creation and maintenance of websites and mobile applications.

This accessibility statement applies to the website onelife.com, the accessibility of which is ‘under development’ in accordance with the criteria of the Web Accessibility Assessment Framework (RAWeb 1.1), which is used on a voluntary basis as a reference for assessing the site’s accessibility.

What is digital accessibility?

Digital accessibility involves making online content and services usable by everyone, regardless of their functional limitations (visual, hearing, motor, cognitive, etc.). This involves adapting websites so that they can be navigated and understood by assistive technologies such as screen readers, speech recognition software and other assistive devices.

Digital accessibility is therefore a set of rules and best practices covering, in particular, functional, graphical, technical and editorial aspects. Adhering to these rules and best practices ensures that digital media (websites, mobile apps, PDF documents, etc.) are accessible to people with disabilities.
For further information on RAWeb 1.1 and best practices for digital accessibility, please visit the official website of the Web Accessibility Assessment Framework (RAWeb 1.1).

Compliance status

The OneLife website onelife.com is currently partially compliant with RAWeb 1.1 (Web Accessibility Assessment Framework) due to the non-conformities and exemptions listed below.

Test results

The compliance audit carried out by Ipedis reveals that the compliance rate is 57.58%:

• 38 criteria are met
• 28 criteria are not met
• 70 criteria are not applicable

Inaccessible content

Non-compliance

Several instances of non-compliance are described in this document, some of which recur across multiple pages:

• Some informative images lack alternative text.
• Some decorative images are not skipped by a screen reader.
• Some complex images do not provide a detailed description.
• Some frames (frame, iframe) do not have a title.
• The titles of some frames are present but irrelevant.
• Some information is conveyed by colour alone.
• Some text lacks sufficient contrast with its background.
• Some components or graphic elements lack sufficient contrast with their background.
• Some media (audio, video) do not have a text transcript or audio description.
• The title of some data tables is not correctly associated with the table.
• The text of some links and their context do not make it possible to understand their function or destination.Some interface components are not compatible with screen readers.
• Some status messages are not correctly conveyed to screen readers.
• The title of some pages is not relevant.
• Some language changes are not indicated in the source code (lang attribute).
• Some HTML tags are used solely for visual presentation purposes.
• On some pages, the information is not appropriately structured using headings (h1, h2 elements, etc.).
• On some pages, the document structure is inconsistent (landmark regions).
• Some CSS declarations for background colour and font are missing.
• On some elements, the focus is not visible when navigating by keyboard.
• Some information is conveyed solely through shape, size or position.Some form fields lack labels.Some form fields do not validate input correctly.
• Some form fields do not offer suggestions for correcting input errors.
• Some pages do not provide at least two navigation methods (menu, site map, search, etc.).
• On some pages, there is no direct link to the content.
• On some pages, the tab order is inconsistent.
• Some office documents are not accessible and have no alternative.

Exemptions due to disproportionate burden

No exemptions identified

Content not subject to accessibility requirements

No content is exempt from accessibility requirements

Preparation of this statement

This statement was prepared on 23 March 2026.

Technologies used to build the website

• HTML5
• CSS
• JavaScript

Web page testing was carried out using the following combinations of user agents and screen readers

NVDA with Google Chrome

The following tools were used during the assessment

• Web Developer Toolbar
• WCAG Contrast Checker
• Taba11y
• Axe Dev Tool – Web Accessibility Testing
• RGAA Assistant
• PDF Accessibility Checker (PAC) 2024

Pages of the website that have been checked for compliance

• Accessibility
• Home
• Contact
• Legal mentions
• News
• Cookies
• Documents
• News example
• History
• IT Software Engineer
• Investment

OneLife is committed to keeping this statement up to date, in line with technical developments and user feedback.