Wavestone is aware that there are accessibility problems on the current site.

Wavestone has long been committed to a CSR approach and has made it a key part of its corporate strategy. Wavestone must now align its societal commitments and its disability support policy, with its digital strategy and has made the digital accessibility of its website a major concern.

Wavestone is committed to making its website accessible in accordance with article 47 of the law n° 2005-102 of February 11, 2005.

To this end, it is implementing the following strategy and actions:

  • A complete overhaul of the website, launched at the end of 2022, which should result in a website with a minimum level of accessibility of 80% in compliance with the RGAA
  • The development of its multi-year accessibility plan and annual action plans, currently under construction, which will be made available on the website

This accessibility statement applies to the website:


Compliance Status

Wavestone is not in compliance with the General Accessibility Guidelines (RGAA) version 4. The non-conformities are listed below.

Test results

The RGAA 4.1 compliance audit carried out by the Temesis company reveals that:

  • 23.61% of the RGAA criteria are met.

In detail:

  • Number of compliant criteria: 17
  • Number of non-applicable criteria: 34
  • Number of non-compliant criteria: 55

Non-Accessible Content

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

Non compliance

List of non-compliant criteria:

  • 1.1 Does each information-bearing image have a text alternative?
  • 1.2 Is each decorative image properly ignored by assistive technologies?
  • 1.3 For each information-bearing image with a textual alternative, is the alternative relevant (excluding special cases)?
  • 1.6 Does each information-bearing image have a detailed description, if necessary?
  • 1.8 Each information-bearing text image, in the absence of a replacement mechanism, should be replaced by styled text where possible. Is this rule respected (excluding special cases)?
  • 2.1 Does each frame have a frame title?
  • 2.2 For each frame with a frame title, is that frame title relevant?
  • 3.1 On each web page, information should not be given by color alone. Is this rule being followed?
  • 3.2 In each web page, is the contrast between the color of the text and the color of its background high enough (excluding special cases)?
  • 3.3 In each web page, are the colors used in the interface components or graphic elements carrying information sufficiently contrasted (excluding special cases)?
  • 4.1 Does each prerecorded time-based media have, if necessary, a textual transcription or audio description (excluding special cases)?
  • 4.3 Does each pre-recorded synchronized time-based media have synchronized subtitles, if necessary (excluding special cases)?
  • 4.4 For each pre-recorded time-synchronized media with synchronized subtitles, are these subtitles relevant?
  • 4.7 Is each temporal media clearly identifiable (excluding special cases)?
  • 5.1 Does each complex data table have a summary?
  • 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 row header correctly reported?
  • 5.7 For each data table, is the appropriate technique to associate each cell with its headers used (excluding special cases)?
  • 6.1 Is each link explicit (excluding special cases)?
  • 6.2 In each web page, does each link have a heading?
  • 7.1 Is each script, if necessary, compatible with assistive technologies?
  • 7.3 Is each script controllable by keyboard and any pointing device (excluding special cases)?
  • 7.4 For each script that initiates a context switch, is the user notified or given control?
  • 7.5 In 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 specified document type (excluding special cases)?
  • 8.6 For each web page with a page title, is the title relevant?
  • 8.7 In each web page, is each language change indicated in the source code (excluding special cases)?
  • 8.9 In each web page, the tags should not be used only 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 In each web page, is the structure of the document consistent (excluding special cases)?
  • 9.3 In each web page, is each list properly structured?
  • 9.4 In each web page, is each citation correctly indicated?
  • 10.1 On the website, are style sheets used to control the presentation of information?
  • 10.2 In each web page, does visible content carrying information remain when style sheets are disabled?
  • 10.4 In each web page, does the text remain readable when the font size is increased to at least 200% (excluding special cases)?
  • 10.6 In each web page, is every link whose nature is not obvious visible in relation to the surrounding text?
  • 10.7 In each web page, for each element receiving focus, is the focus intake visible?
  • 10.9 In each web page, information should not be given only by shape, size or position. Is this rule respected?
  • 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 focus is taken or when an interface component is hovered over
  • 11.1 Does each form field have a label?
  • 11.4 In each form, are each field label and its associated field joined together (except in special cases)?
  • 11.5 In each form, are fields of the same nature grouped together, if necessary?
  • 11.9 In each form, is the title of each button relevant (excluding special cases)?
  • 11.10 In each form, is the input control used appropriately (excluding special cases)?
  • 11.13 Can the purpose of an input field be inferred to facilitate automatic filling of fields with user data?
  • 12.6 Can content grouping areas present in several web pages (header, main navigation, main content, footer and search engine areas) be reached or avoided?
  • 12.7 In each web page, is there an avoidance or quick access link to the main content area (excluding special cases)?
  • 12.8 Is the tabbing order consistent on each web page?
  • 12.9 In each web page, the navigation should not contain any keyboard traps. Is this rule respected?
  • 13.3 On each web page, is there an accessible version of each office document that can be downloaded (except in special cases)?
  • 13.8 In each web page, is every moving or flashing content controllable by the user?
  • 13.9 In each web page, is the content offered viewable in any screen orientation (portrait or landscape) (excluding special cases)?
  • 13.10 In each web page, are the functionalities that can be used or available by means of a complex gesture also available by means of a simple gesture (except in special cases)?

Content not subject to the accessibility obligation

  • Files available in desktop formats published before September 23, 2018
  • Pre-recorded audio and video content, including content with interactive components, published before September 23, 2020
  • Third-party content that is not funded or developed by the relevant organization and is not under its control (cookie banner, YouTube player)
  • Google maps, provided that, in the case of maps intended to provide a location or route, the essential information is provided in an accessible digital form

Establishment of this declaration of accessibility

This declaration was established on November 22, 2021.

Technologies used for the creation of the website

  • HTML
  • CSS
  • Javascript

Testing environment

The web page tests were performed with the following web browser and screen reader combinations:

  • NVDA 2021.2, Firefox 94
  • Voiceover, Safari

The following tools were used during the evaluation:

  • WCAG contrast checker​
  • HeadingsMap​
  • Web developer​
  • ARC Toolkit

Site pages that were checked for compliance

Feedback and contact

Wavestone, pending the redesign of its website, is committing to take the necessary steps, within a reasonable period of time, to provide access to the information and functionalities sought by the disabled person in compliance with the right to compensation.

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

We invite people who encounter difficulties to send a message to the email address mission.handicap@wavestone.com or using the form https://wwa.wavestone.com/en/contact/


This procedure is to be used in the following case.

You have reported to an accessibility defect that prevents you from accessing content or a service to the disability point of contact and you have not received a satisfactory response.