Skip to content
Omnifloo Office Try

Draft — document under review by a lawyer. This statement will be updated after a full audit.

This translation is provided for information only: the French version of this document is the only legally binding version. Version française

Accessibility statement

Drawn up on 14 October 2026

DYONYSOS SASU is committed to making its Omnifloo Office portal (office.omnifloo.com) accessible, in accordance with the French general accessibility improvement framework (RGAA). This statement applies to the public pages of the portal: home, sign-up, applications, help, information pages and legal pages. It is published voluntarily, in particular for public buyers, without prejudice to the legal obligations that apply to each party.

1. Compliance status

The Omnifloo Office portal is partially compliant with the RGAA.

This wording is deliberately cautious: the portal has not yet undergone a full RGAA audit by an auditor. The checks described below cover only part of the framework's criteria, so no compliance rate is announced.

2. Test results

CheckResult
Automated checkaxe-core 4.10.2 tool, WCAG 2.2 level A and AA rules and best practices, last run on 2026-10-14.
Pages analysed190 pages, in 5 languages, in desktop and mobile display.
Serious violations0 remaining violation(s) of “serious” or “critical” level.
Fixed before publicationHorizontally scrollable regions not reachable by keyboard (tables), pages without a level 1 heading and inconsistent heading order.
Test browserChromium, without extensions.

An automated check detects only part of the accessibility defects. It replaces neither a manual audit of the RGAA criteria nor tests with screen readers, which are planned (see section 7). The check is re-run at every verification of the code repository and fails if a violation of “serious” or “critical” level appears.

3. Inaccessible content and known limitations

  • Document editors (text, spreadsheet, presentation, PDF): they rely on a free component developed by a third party. Their accessibility has not been assessed in this statement; keyboard navigation and screen reader use are partial, and some areas are drawn in a canvas that assistive technologies cannot read.
  • File space, calendar, contacts and other applications of the space: free third-party components, also not assessed here.
  • Documents uploaded or produced by users (files, PDFs): their accessibility depends on their author. The help centre contains pages on creating accessible documents.
  • Demonstration videos: none is published to date; we plan to add subtitles before they go online.

At this stage we are not invoking the exemption for disproportionate burden. The limitations above concern third-party components that we do not fully control; they are flagged so that you can take them into account.

4. Preparation of this statement

  • Technologies used: HTML, CSS, JavaScript and WAI-ARIA attributes.
  • Reference user agents for testing: Chromium, desktop and mobile display.
  • Measures already in place: skip link to the content, visible focus, heading structure, text alternatives, checked contrast, keyboard-accessible scrollable tables, language of each page declared.

5. Feedback and contact

Si vous ne parvenez pas à accéder à un contenu ou à un service, ou si vous constatez un défaut d'accessibilité, écrivez-nous à contact@omnifloo.com en précisant l'adresse de la page, ce que vous n'avez pas pu faire et, si vous en utilisez, votre outil d'assistance. Nous accusons réception sous 2 jours ouvrés et nous vous proposons une alternative accessible ou une réponse sous un mois.

6. Means of redress

This procedure applies in the following case: you have reported to the site manager an accessibility defect that prevents you from accessing content or a service, and you have not obtained a satisfactory reply. You may then contact the French Defender of Rights (Défenseur des droits):

7. Improvement plan

  • Have a full RGAA audit of the portal carried out by an auditor, then publish the compliance rate and a multi-year plan.
  • Test the main journeys (sign-up, login, opening a document) with screen readers and keyboard only.
  • Assess the accessibility of the document editors and document their limitations and workarounds.