Digital Accessibility

Web accessibility for all

1/ What is Web accessibility? 

Digital accessibility refers to the practice of making a service accessible to as many people as possible. This means making content accessible to all people from any device (computer, tablet, mobile phone, etc.), whatever their network infrastructure, geographical location, or physical or mental ability. Very closely associated with eco-friendly design, making a website accessible requires the implementation of a number of rules.  

The French government has drafted its Référentiel général d’amélioration de l’accessibilité (RGAA) (General rules for the improvement of accessibility) to encourage players in the sector to optimise website accessibility. This is the reference document that the Kereis Group has decided to adhere to when developing its websites. 

 

2/ RGGA accessibility statement

Kereis is committed to making its websites accessible in compliance with article 47 of French law no. 2005-102 dated 11 February 2005. 

To this end, it implements the following strategy and actions: 

  • 2022-2023 multiannual accessibility scheme (to be provided), 
  • Actions carried out in 2022 (to be provided), 
  • 2022-2023 action plan (to be provided). 

This accessibility statement applies to the kereis.com website. 

 

A/ Compliance status

The Kereis Group website (kereis.com) is partially compliant with the RGAA (version 4.0) due to the non-conformities and dispensations listed below.

 

B/ Test results 

The compliance audit conducted in December 2022, determined partial compliance of the website. :

  • 72,8% of RGAA version 4.0 criteria are complied with.

 

C/ Non-accessible content (partial compliance)

Non-compliance  

  • 1.8 Each text image carrying information, in the absence of a replacement mechanism, must if possible be replaced by stylized text. Is this rule respected (except in special cases)?
  • 4.1 Does each pre-recorded time-based medium have a textual transcription or audio description, if necessary (except in special cases)?
  • 4.2 For each pre-recorded time-lapse media with a synchronized text transcript or audio description, are they relevant (excluding special cases)?
  • 4.5 Does each pre-recorded time-lapse media have a synchronized audio description, if necessary (excluding special cases)?
  • 4.6 For each pre-recorded temporal media with a synchronized audio description, is it relevant?
  • 4.11 Is the viewing of each time-based medium, if necessary, controllable by keyboard and any pointing device?
  • 4.13 Is each temporal and non-temporal media compatible with assistive technologies (excluding special cases)?
  • 5.7 For each data table, is the appropriate technique used to associate each cell with its headers (excluding special cases)?
  • 5.8 Each formatting table should not use elements specific to data tables. Is this rule respected?
  • 7.1 Is each script, if necessary, compatible with assistive technologies?
  • 7.2 For each script that has an alternative, is the alternative relevant?
  • 7.3 Is each script controllable by the keyboard and by any pointing device (except in special cases)?
  • 8.9 In each web page, tags should not be used for presentation purposes only. Is this rule respected?
  • 10.3 In each web page, is the information still understandable when style sheets are disabled?
  • 10.9 In each web page, information should not be given by shape, size, or position alone. Is this rule respected?
  • 10.10 In every web page, information should not be given by shape, size, or position alone. Is this rule implemented appropriately?
  • 10.11 For each web page, can the contents be presented without using both vertical scrolling for a window with a height of 256px or horizontal scrolling for a window with a width of 320px (excluding special cases)?
  • 10.12 In each web page, can the text spacing properties be redefined by the user without loss of content or functionality (excluding special cases)?
  • 10.13 In each web page, is the additional content that appears when the user focuses on or hovers over an interface component controllable by the user (excluding special cases)?
  • 10.14 In each web page, can the additional contents appearing via CSS styles only be made visible with the keyboard and any pointing device?
  • 12.7 In each web page, is there an avoidance or quick access link to the main content area (excluding special cases)?
  • 13.3 In each web page, is there an accessible version of each office document that can be downloaded (except in special cases)?
  • 13.4 For each office document with an accessible version, does this version offer the same information?
  • 13.11 In each web page, can the actions triggered by a pointing device on a single point on the screen be cancelled (except in special cases)?
  • 13.12 In each web page, can the functionalities that involve a movement of the device or towards the device be satisfied in an alternative way (excluding special cases)?

D/ Technologies used to produce kereis.com

  • HTML 5 ; 
  • CSS 3 ; 
  • Javascript (including Jquery) ;
  • BACKBONE ;
  • REACT.

 

E/ Test environment

The content upload checks were conducted based on the combination provided by the RGAA 4.0 baseline, with the following versions:

  • Google Chrome version 105.x 

Tools to assess accessibility: 

  • Plugin GreenIT analysis
  • Plugin Accessibility Insights for Web 
  • W3C Validator 
  • Google Page Speed Insight 

Website pages that have been checked for compliance:

For the pages not listed above, the accessibility and compliance audits still need to be carried out. The website has a list of pre-established text blocks that are used on all pages to ensure an overall coherent accessibility and consistency.

F/ Drawing up of this accessibility statement

This statement was drawn up on 13/12/2022. It was updated on 21/12/2022. 

 

G/ Feedback and contact

If you experience difficulty accessing content or a service, please contact us so that we can provide you with an accessible alternative or to obtain the content in another format: contact page.

 

H/ Appeals

This procedure should be used if, despite reporting an accessibility fault that is preventing you from accessing content or one of the portal services, to the website administrator, your issue has not been resolved to your satisfaction.

3/ PageSpeed Insights

Kereis.com obtained an average score of 98,5/100 from a computer and 97,5/100 from a mobile phone for its website pages.

The analysis was carried out on 6 pages on 13 December 2022 using Google’s PageSpeed Insights tool. This tool generates user experience reports for pages accessed via mobile devices and computers, and provides suggestions on how to improve these pages. 

Google developed an algorithm to display the most relevant content at the top of the search results. Since 2021, this algorithm has also taken Core Web Vitals into account in order to ensure the fast loading of pages, particularly on mobile devices. The PageSpeed Insight score is partially calculated based on these vitals:

  • Page performance
  • Page interactivity
  • Page stability

*Here is the list of pages tested and the associated scores: