Accessibility statement

Last update: August 14, 2024

At Oney, we are committed to ensuring that our website is accessible to all users in accordance with Article 47 of the French law (No. 2005-102) of 11 February 2005.

With this in mind, we pursue the following strategy and actions : Accessibility schema 2024

This accessibility statement is valid for the website: https://docs.oney.com/

Conformance status

Oney is partially conformant with the French general accessibility improvement guidelines (Référentiel Général d’Amélioration de l’Accessibilité – RGAA), as certain parts of our website do not fully conform with the guidelines, as listed below.

Test results

Oney Docs is not in compliance with the general guidelines for improving accessibility. The non-compliances are listed below.

The RGAA 4.1.2 compliance audit carried out by Temesis revealed that:

29.41% of the RGAA criteria have been met.

In detail:

  • Number of compliant criteria: 15
  • Number of non-compliant criteria: 36
  • Number of criteria not applicable: 55

Inaccessible content

The content listed below is not accessible for the following reasons:

List of non-compliant criteria :

1.2 - Is each decorative image correctly ignored by assistive technologies?

1.3 - For each information-bearing image with a text alternative, is this alternative relevant (excluding special cases)?

1.6 - If necessary, does each information-bearing image have a detailed description?

1.8 - In the absence of a replacement mechanism, each information-carrying text image should, if possible, be replaced by styled text. Is this rule respected (excluding special cases)?

3.1 - In every web page, information must not be provided solely by colour. Is this rule respected?

3.2 - On each web page, is the contrast between the colour of the text and the colour of its background high enough (excluding special cases)?

3.3 - In each web page, are the colours used in the interface components or information-carrying graphic elements sufficiently contrasting (excluding special cases)?

4.1 - If necessary, does each pre-recorded time-based medium have a text transcription or audio description (excluding special cases)?

4.3 - Does each pre-recorded time-synchronised medium have synchronised subtitles, if necessary (excluding special cases)?

5.3 - For each formatting table, is the linearized content still comprehensible?

5.4 - For each data table with a title, is the title correctly associated with the data table?

5.6 - For each data table, are each column header and each row header correctly declared?

6.1 - Is each link explicit (excluding special cases)?

6.2 - Is there a heading for each link on each web page?

7.1 - If necessary, is each script compatible with assistive technologies?

7.3 - Can each script be controlled by the keyboard or any other pointing device (except in special cases)?

7.5 - On each web page, are status messages correctly rendered by assistive technologies?

8.2 - For each web page, is the generated source code valid for the type of document specified (excluding special cases)?

8.9 - In each web page, tags must not be used solely for presentation purposes. Is this rule respected?

9.1 - In each web page, is the information structured by the appropriate use of headings?

9.2 - On each web page, is the structure of the document consistent (excluding special cases)?

9.3 - Is each list correctly structured on each web page?

10.2 - On each web page, is the visible content that provides information still present when the style sheets are deactivated?

10.4 - In each web page, is the text still legible when the font size is increased to at least 200% (excluding special cases)?

10.7 - On each web page, is the focus visible for each element that receives focus?

10.11 - For each web page, can the content be presented without loss of information or functionality and without having to scroll vertically for a 256 px high window or horizontally for a 320 px wide window (excluding special cases)?

10.12 - In each web page, can text spacing properties be redefined by the user without loss of content or functionality (excluding special cases)?

10.14 - In each web page, can additional content appearing via CSS styles only be made visible using the keyboard and any pointing device?

11.1 - Does each form field have a label?

11.2 - Is each label associated with a form field relevant (excluding special cases)?

12.1 - Does each set of pages have at least two different navigation systems (excluding special cases)?

12.6 - Can content grouping zones present on several web pages (header, main navigation, main content, footer and search engine zones) be reached or avoided?

12.7 - Is there an avoidance or quick access link to the main content area on each web page (excluding special cases)?

12.8 - On each web page, is there an alternative to the order of your emoticon or cryptic syntax?

Content not subject to accessibility requirements

Files available in office formats published before 23 September 2018;

Third-party content that is not funded or developed by the organisation concerned and is not under its control:

Feedback Hotjar

Establishment of this declaration of accessibility

This declaration was drawn up on 22 November 2023.

Technologies used to create the website

  • HTML
  • CSS
  • Javascript

Test environment

The web page tests were carried out with the following combinations of web browsers and screen readers:

  • NVDA 2023.1, Firefox 119
  • Jaws 2022, Firefox 119
  • Voiceover, Safari

The following tools were used during the evaluation:

  • WCAG contrast checker
  • HeadingsMap
  • Web developer
  • Stylus
  • Colour Contrast Analyser

Web pages tested for conformance

Home page - https://docs.oney.com/

Information about cookies https://docs.oney.com/information-about-cookies

FAQ https://oney1185.zendesk.com/hc/fr

Payment Solutions https://docs.oney.com/catalogs/digital_payments/payment_solutions

Payment Solutions - 3x 4x Payment https://docs.oney.com/docs/digital_payments/payment_solutions/3x_4x_payment

Financial report V2 - Technical information https://docs.oney.com/docs/digital_payments/financial_report/financial_report_v2/technical_information

Direct Integration - Overview https://docs.oney.com/docs/platforms_plugins/direct_integration/custom_integration/custom_integration_overview

CMS - Magento - Last plugin https://docs.oney.com/docs/platforms_plugins/cms_integration/magento_2/last_plugin

CMS - Magento - Plugin Configuration https://docs.oney.com/docs/platforms_plugins/cms_integration/magento_2/plugin_configuration

API - Oney Marketing API (1.0) https://docs.oney.com/docs/developer_ressources/apis/marketing_api/marketing_api_v1.0

Feedback and contact

If you encounter any problems accessing content or a service on this website, please contact the site manager using the contact form available on www.partners.oney.com so that we can direct you towards an accessible alternative or provide you with the content in another form.

Complaint mechanisms

This procedure may be used in the following case.

If you have already alerted the site manager to an accessibility issue on the website which prevents you from accessing the content or a service, and you have not received a satisfactory response.

You can write to the Defender of Rights (https://formulaire.defenseurdesdroits.fr/formulaire_saisine/?locale=en_GB).

You can contact a representative of the Defender of Rights near you (https://www.defenseurdesdroits.fr/carte-des-delegues)

You can send a letter (freepost – no stamp needed) to:
Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07

Did you find this content useful ?