Digital accessibility

Accessibility statement of the website www.cic-cib.com

CIC Corporate & Institutional Banking undertakes to make accessible its websites, Intranet, Extranet and mobile applications as per Directives (EU) 2019/882 and 2016/2012 pertaining to the accessibility requirements for products and services and its national transposition provisions.

To this end, CIC Corporate & Institutional Banking implements a strategy and actions set out in its multi-year scheme and provides a page dedicated to accessibility.

Conformity status

Website www.cic-cib.com is partly compliant with version 4.1.2 of the RGAA (general accessibility improvement standard) due to nonconformities listed below.

Test results

The accessibility audit was performed by Temesis in 09/2026.

It reveals that 62,69% of the criteria is complied with.

This percentage corresponds to:

  • 42 compliant criteria
  • 25 non-compliant criteria
  • 39 criteria not applicable

The average website compliance rate is of 85,00%.

Inaccessible content

Some content of the website is not accessible for the following reasons:

Non-compliances

  • 1.2 Are all decorative images correctly ignored by assistive technologies ?
  • 2.1 Dœs every frame have a frame title ?
  • 3.2 On every web page, is the contrast between the text colour and the background colour sufficiently high (excluding special cases) ?
  • 4.2 For each pre-recorded media file with a text transcript or synchronised audio description, are these relevant (except in special cases) ?
  • 6.1 Is every link self-explanatory (except in special cases) ?
  • 7.1 Is every script, where necessary, compatible with assistive technologies ?
  • 7.3 Can each script be controlled using a keyboard and any pointing device (except in special cases) ?
  • 7.5 On each web page, are status messages correctly rendered by assistive technologies ?
  • 8.6 For each web page with a page title, is that title relevant ?
  • 8.7 On each web page, is every change of language indicated in the source code (excluding special cases) ?
  • 8.9 On each web page, tags must not be used solely for presentational purposes. Is this rule being followed ?
  • 9.1 On each web page, is the information structured through the appropriate use of headings ?
  • 9.3 On each web page, is every list correctly structured ?
  • 10.1 Are style sheets used on the website to control the presentation of information ?
  • 10.7 On each web page, for every element that receives focus, is the focus indicator visible ?
  • 10.11 For each web page, can the content be displayed without any loss of information or functionality and without requiring either vertical scrolling for a window with a height of 256 px or horizontal scrolling for a window with a width of 320 px (excluding special cases) ?
  • 10.13 On every web page, can the user control any additional content that appears when focus is gained or when the mouse hovers over an interface component (excluding special cases) ?
  • 11.1 Dœs each form field have a label ?
  • 11.4 In each form, are each field label and its associated field placed side by side (except in special cases) ?
  • 11.10 In each form, are input validation checks used appropriately (except in special cases) ?
  • 11.11 In each form, is the input control accompanied, where necessary, by suggestions to help correct input errors ?
  • 11.13 Can the purpose of an input field be inferred to facilitate the automatic completion of fields with the user’s data ?
  • 12.7 On every web page, is there a skip link or quick access link to the main content area (excluding special cases) ?
  • 12.8 On every web page, is the tab order consistent ?
  • 13.3 On every web page, dœs every downloadable office document have an accessible version, where necessary (excluding special cases) ?

Exemptions due to disproportionate burden

No exceptions

Content not subject to the accessibility obligation

  • No content not subject to accessibility requirements

Preparation of the accessibility statement

This statement was prepared on 23/09/2026.

Technologies used for making of the website

  • HTML 5
  • CSS
  • Javascript

User agents, assistive technology and tools used to verify accessibility

Web page tests were performed with the following combination or combinations of screen readers and web browsers:

  • NVDA 2026.1 on Firefox 156.0
  • Jaws 2025 on Firefox 156.0
  • Voiceover and iOS 14.6.1
  • Voiceover iOS 17.71

The following tools were used during the assessment:

  • WCAG contrast checker
  • HeadingsMap
  • Web developer
  • Stylus

Pages that have undergone a conformity verification

Feedback and contact

If you have trouble using our services, please get in touch with us.

You are disabled and have difficulty using our services, contact the CIC Corporate & Institutional Banking accessibility contact.
To remedy the issue durably and within reason, online correction of the accessibility fault will be prioritised. If this cannot be done, the desired information will be communicated to you in an accessible format, as you wish: either in writing – document or email, or spoken during a face-to-face meeting or phone call.

Right of review

If the response provided does not satisfy you, you have the possibility to file a complaint or to contact the mediator. To file a complaint, various remedies are available to you: