Accessibility Statement

Accessibility Statement

Accessibility Statement

↳ Company Identification

Insign is committed to making its site www.insign.fr accessible in accordance with Article 47 of Law No. 2005-102 of February 11, 2005.

This accessibility statement applies to www.insign.fr.

Insign is committed to making its site www.insign.fr accessible in accordance with Article 47 of Law No. 2005-102 of February 11, 2005.

This accessibility statement applies to www.insign.fr.

Compliance Status

The website www.insign.fr is partially compliant with the general accessibility improvement framework (RGAA version 4.1.2).

The website www.insign.fr is partially compliant with the general accessibility improvement framework (RGAA version 4.1.2).

Test Results

The compliance audit conducted reveals that 80% of the RGAA criteria are met.

  • Number of applicable criteria: 70

  • Number of compliant criteria: 56

  • Number of non-compliant criteria: 14

The compliance audit conducted reveals that 80% of the RGAA criteria are met.

  • Number of applicable criteria: 70

  • Number of compliant criteria: 56

  • Number of non-compliant criteria: 14

The compliance audit conducted reveals that 80% of the RGAA criteria are met.

  • Number of applicable criteria: 70

  • Number of compliant criteria: 56

  • Number of non-compliant criteria: 14

Content Not Accessible

The main non-conformities identified are related to:

  • 2.2 Does each frame with a frame title have a relevant title?

  • 4.13 Is each time-based and non-time-based media compatible with assistive technologies (except for certain cases)?

  • 7.5 On each web page, are status messages correctly conveyed by assistive technologies?

  • 8.2 For each web page, is the generated source code valid according to the specified document type?

  • 8.7 On each web page, is every change in language indicated in the source code (except for certain cases)?

  • 10.2 On each web page, does the visible content carrying information remain present when stylesheets are disabled?

  • 10.3 On each web page, does the information remain understandable when stylesheets are disabled?

  • 10.10 On each web page, information should not only be conveyed by shape, size, or position. Is this rule implemented effectively?

  • 11.6 In each form, does each grouping of similar fields have a legend?

  • 11.11 In each form, is input validation accompanied, if necessary, by suggestions that facilitate the correction of input errors?

  • 12.1 Does each set of pages have at least two different navigation systems (except for certain cases)?

  • 12.11 On each web page, are additional contents that appear on hover, focus, or activation of an interface component keyboard accessible if necessary?

  • 13.8 On each web page, can each moving or blinking content be controlled by the user?

  • 13.10 On each web page, can functionalities available or operable through complex gestures also be available through simple gestures (except for certain cases)?

The main non-conformities identified are related to:

  • 2.2 Does each frame with a frame title have a relevant title?

  • 4.13 Is each time-based and non-time-based media compatible with assistive technologies (except for certain cases)?

  • 7.5 On each web page, are status messages correctly conveyed by assistive technologies?

  • 8.2 For each web page, is the generated source code valid according to the specified document type?

  • 8.7 On each web page, is every change in language indicated in the source code (except for certain cases)?

  • 10.2 On each web page, does the visible content carrying information remain present when stylesheets are disabled?

  • 10.3 On each web page, does the information remain understandable when stylesheets are disabled?

  • 10.10 On each web page, information should not only be conveyed by shape, size, or position. Is this rule implemented effectively?

  • 11.6 In each form, does each grouping of similar fields have a legend?

  • 11.11 In each form, is input validation accompanied, if necessary, by suggestions that facilitate the correction of input errors?

  • 12.1 Does each set of pages have at least two different navigation systems (except for certain cases)?

  • 12.11 On each web page, are additional contents that appear on hover, focus, or activation of an interface component keyboard accessible if necessary?

  • 13.8 On each web page, can each moving or blinking content be controlled by the user?

  • 13.10 On each web page, can functionalities available or operable through complex gestures also be available through simple gestures (except for certain cases)?

The main non-conformities identified are related to:

  • 2.2 Does each frame with a frame title have a relevant title?

  • 4.13 Is each time-based and non-time-based media compatible with assistive technologies (except for certain cases)?

  • 7.5 On each web page, are status messages correctly conveyed by assistive technologies?

  • 8.2 For each web page, is the generated source code valid according to the specified document type?

  • 8.7 On each web page, is every change in language indicated in the source code (except for certain cases)?

  • 10.2 On each web page, does the visible content carrying information remain present when stylesheets are disabled?

  • 10.3 On each web page, does the information remain understandable when stylesheets are disabled?

  • 10.10 On each web page, information should not only be conveyed by shape, size, or position. Is this rule implemented effectively?

  • 11.6 In each form, does each grouping of similar fields have a legend?

  • 11.11 In each form, is input validation accompanied, if necessary, by suggestions that facilitate the correction of input errors?

  • 12.1 Does each set of pages have at least two different navigation systems (except for certain cases)?

  • 12.11 On each web page, are additional contents that appear on hover, focus, or activation of an interface component keyboard accessible if necessary?

  • 13.8 On each web page, can each moving or blinking content be controlled by the user?

  • 13.10 On each web page, can functionalities available or operable through complex gestures also be available through simple gestures (except for certain cases)?

↳ Exceptions for Disproportionate Burden

Nothing.

Nothing.

Nothing.

Content not required to meet accessibility standards

Nothing.

Nothing.

Nothing.

Creating this accessibility statement

This statement was made on October 3, 2025.

Technologies used in the development of the website

  • HTML5

  • CSS

  • Javascript

Testing Environment

The content display checks were carried out based on the combination provided by the RGAA reference base, with the following versions: Safari Version 18.5 - VoiceOver

Tools used during the evaluation

  • HeadingsMap

  • WCAG Color Contrast Checker

  • WAVE Web Accessibility Evaluation Tools

  • Browser Inspector

  • DevTools

Pages of the site subject to compliance verification

This statement was made on October 3, 2025.

Technologies used in the development of the website

  • HTML5

  • CSS

  • Javascript

Testing Environment

The content display checks were carried out based on the combination provided by the RGAA reference base, with the following versions: Safari Version 18.5 - VoiceOver

Tools used during the evaluation

  • HeadingsMap

  • WCAG Color Contrast Checker

  • WAVE Web Accessibility Evaluation Tools

  • Browser Inspector

  • DevTools

Pages of the site subject to compliance verification

This statement was made on October 3, 2025.

Technologies used in the development of the website

  • HTML5

  • CSS

  • Javascript

Testing Environment

The content display checks were carried out based on the combination provided by the RGAA reference base, with the following versions: Safari Version 18.5 - VoiceOver

Tools used during the evaluation

  • HeadingsMap

  • WCAG Color Contrast Checker

  • WAVE Web Accessibility Evaluation Tools

  • Browser Inspector

  • DevTools

Pages of the site subject to compliance verification

Feedback and Contact

If you can't access content or a service, feel free to contact the website manager at www.insign.fr to be directed to an accessible alternative or to get the content in another format.

If you can't access content or a service, feel free to contact the website manager at www.insign.fr to be directed to an accessible alternative or to get the content in another format.

If you can't access content or a service, feel free to contact the website manager at www.insign.fr to be directed to an accessible alternative or to get the content in another format.

Options for Recourse

Use this procedure in the following situation.

You've informed the website manager about an accessibility issue that prevents you from accessing content or services on the portal, and you haven't received a satisfactory response.

Use this procedure in the following situation.

You've informed the website manager about an accessibility issue that prevents you from accessing content or services on the portal, and you haven't received a satisfactory response.

Use this procedure in the following situation.

You've informed the website manager about an accessibility issue that prevents you from accessing content or services on the portal, and you haven't received a satisfactory response.