Home   >   General Repository for Improving Accessibility (RGAA)
accessibility

General Repository for Improving Accessibility (RGAA)

Accessibility Statement

Saipol is committed to making its services accessible, in accordance with Article 47 of Law No. 2005-102 of 11 February 2005.

To this end, it is implementing a strategy and actions detailed in its multi-year accessibility plan, currently being drafted.

This accessibility statement applies to the Saipol website.

State of Compliance

The Saipol website is non-compliant with WCAG 4.1 level Double-A (AA) due to the non-conformities and exemptions listed below.

Test results

The accessibility audit conducted by Ipedis revealed a compliance rate of 37.31%:

  • 25 criteria are compliant

  • 42 criteria are non-compliant

  • 39 criteria are not applicable

Non-Accessible Content

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

Non-Compliance

Several accessibility issues are described in this document, some of which occur repeatedly across multiple pages:

  • Some informative images do not have text alternatives.

  • Some decorative images are not ignored by screen readers.

  • Some complex images lack detailed descriptions.

  • Some image captions are not properly linked (<figure> element).

  • Some information is conveyed by color only.

  • Some text has insufficient contrast with its background.

  • Some components or graphical elements have insufficient contrast with their background.

  • Some media (audio or video) do not have transcripts or audio descriptions.

  • Some videos do not have subtitles.

  • Some media (audio or video) are not clearly identified as such by screen readers.

  • The label or context of some links does not make their function or destination clear.

  • Some links have no labels.

  • Some scripts are not compatible with screen readers.

  • Some scripts cannot be controlled via keyboard.

  • Some context changes are not announced or controllable by the user.

  • Some status messages are not correctly conveyed to screen readers.

  • Some pages contain invalid source code: writing rules, element opening/closing, nesting, or duplicate ID attributes.

  • Some page titles are not relevant.

  • Some HTML tags are used solely for visual presentation.

  • On some pages, information is not properly structured with headings (h1, h2, etc.).

  • On some pages, document structure (landmark regions) is inconsistent.

  • Some lists are not properly marked up as lists.

  • Some quotes are not properly marked up as quotations.

  • The visual presentation of information relies on HTML elements rather than CSS.

  • Some information disappears when CSS is disabled.

  • Some information becomes unintelligible when CSS is disabled.

  • Some text becomes unreadable when font size is increased to 200%.

  • Some non-obvious links are not highlighted with contrasting color or visual change on keyboard focus or mouse hover.

  • For some elements, keyboard focus is not visible.

  • Some invisible content is unnecessarily read by screen readers.

  • Some information is conveyed only through shape, size, or position.

  • Some content that appears on focus or hover cannot be controlled by the user.

  • Some additional content displayed via CSS only is not visible when navigating by keyboard.

  • Some form fields have no labels.

  • Some form fields do not properly control data entry.

  • Some form fields do not facilitate autocomplete.

  • Some page regions are not marked up as such.

  • Some pages have no skip link to main content.

  • On some pages, the tab order is inconsistent.

  • Some additional content that appears on keyboard focus or mouse hover is not reachable by keyboard.

  • Some office documents are not accessible and have no alternative.

  • Some moving content cannot be controlled by the user.

Exemptions for Disproportionate Burden

No exemptions identified.

Content Not Subject to Accessibility Requirements

No content identified as not subject to the accessibility obligation.

Preparation of this Accessibility Statement

This statement was prepared on July 30, 2025.

Technologies Used to Build the Website:

  • HTML5

  • CSS

  • JavaScript

Pages Were Tested Using the Following Browser and Screen Reader Combinations:

  • NVDA with Firefox

  • NVDA with Chrome

Tools Used During Evaluation:

  • Accessible Color Picker

  • Assistant RGAA

  • Axe DevTools – Web Accessibility Testing

  • Grammalecte

  • HeadingsMap

  • InspecteurA11y

  • Ipedis Audit Tool

  • PAC 2024 – PDF Accessibility Checker

  • Stylus

  • Taba11y

  • Tanaguru Webext

  • WCAG – Contrast Checker

  • Web Developer Toolbar

Pages Reviewed for Compliance

Improvement and contact

If you are unable to access a content or service, you can contact the website manager to be directed to an accessible alternative or obtain the content in another form.

Contact the Communication Department at: RGAA@avril.com

Recourse

This procedure should be used in the following situation:

You have reported an accessibility issue to the website manager that prevents you from accessing content or services, and you have not received a satisfactory response.

  • Send a message to the Defender of Rights

  • Contact the regional delegate of the Defender of Rights

  • Send a letter by post (free of charge, no stamp required) to:
    Défenseur des droits
    Libre réponse 71120
    75342 Paris CEDEX 07

Would you like more information?
Contact us