Accessibility: non-compliant

What is Digital Accessibility?

An accessible website is designed to allow people with disabilities to fully enjoy its content and functionalities, without encountering obstacles.

For example, an accessible site offers the possibility of:

  • Use a voice synthesis or braille beach, essential tools for blind or visually impaired people.
  • Adapt the display to suit the specific needs of each, such as enlarging characters or adjusting colors.
  • Navigate without using a mouse, using only a keyboard, touch screen, voice control or any other suitable device.

To ensure this accessibility, the site must meet the standards in force when it is completed and updated.

 

STATEMENT OF ACCESSIBILITY

Crédit Agricole - Indosuez France undertakes to make its website accessible in accordance with article 47 of Law n° 2005-102 of 11 February 2005.

To this end, it implements the following strategy and actions: multi year plan and action plan for the current year, including an assessment of the actions carried out the previous year.

This declaration of accessibility applies to the following website :
https://france.ca-indosuez.com/
 

COMPLIANCE STATUS

Indosuez France does not comply with the general accessibility improvement framework. Non compliances are listed below.

 

TEST RESULTS

The RGAA 4.1.2 compliance audit conducted by Temesis revealed that:

  • 34.43% of the RGAA criteria are met.

In details :

  • Number of criteria met: 21
  • Number of non compliant criteria: 40
  • Number of criteria not applicable: 45


INACCESSIBLE CONTENT

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


Non compliance

List of non compliant criteria:

  • 1.3 Is this alternative relevant for each informational image with a textual alternative (except in specific cases)?
  • 3.1 In each web page, colour is not the only way to display information. Is this rule respected?
  • 3.2 In each web page, is the contrast between the colour of the text and the colour of the background high enough (except in specific cases)?
  • 3.3 In each web page, are the colours used in the interface components or in the graphics containing information sufficiently contrasted (except in specific cases)?
  • 5.3 For each layout chart, is the linear layout still understandable?
  • 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 declared?
  • 6.1 Is each link explicit (excluding specific cases)?
  • 6.2 Does each link have a title on each webpage?
  • 7.1 Is every script supported, if needed?
  • 7.3 Is each script controllable using a keyboard and a pointing device (except in specific cases)?
  • 7.4 For each script that initiates a change of context, is the user notified or has he or she control?
  • 7.5 In each web page, are status messages correctly rendered by assistive technology?
  • 8.6 Is this title relevant for each page with a page title?
  • 8.7 Is every language change on each webpage indicated in the source code (except in specific cases)?
  • 8.9 In each web page, the tags must not be used solely for presentation purposes. Is this rule respected?
  • 9.1 On each webpage, is the information structured by the appropriate use of securities?
  • 9.2 Is the structure of the document consistent in each web page (excluding specific cases)?
  • 9.3 Is each list on each web page structured correctly?
  • 9.4 On each web page, is every quote correctly stated?
  • 10.1 Are style sheets used on the Website to control how information is displayed?
  • 10.2 Does information carrying visible content in each web page remain present when style sheets are disabled?
  • 10.3 On each web page, is the information still understandable when style sheets are disabled?
  • 10.7 On each web page, is focus visible for each item?
  • 10.8 For each web page, is hidden content intended to be ignored by assistive technology?
  • 10.9 In each web page, information must not be given solely by form, size or position. Is this rule respected?
  • 10.12 Can users redefine text spacing properties on each web page without losing content or functionality (except in specific cases)?
  • 10.13 In each web page, can the user control additional content that appears when they focus or overlook an interface component (except in specific cases)?
  • 10.14 In each web page, can additional content appearing via CSS styles only be made visible by the keyboard and any pointing devices?
  • 11.1 Does each form field have a label?
  • 11.9 Is the name of each button relevant in each form (except in a specific case)?
  • 11.10 Is the input control used in a meaningful way in each form (excluding specific cases)?
  • 11.11 In each form, is the input control accompanied, if necessary, by suggestions to facilitate the correction of input errors?
  • 11.13 Can the purpose of an input field be deducted to facilitate the automatic filling of fields with user data?
  • 12.6 Can content bundling areas across multiple web pages (header, primary browser, primary content, footer, and search engine areas) be reached or avoided?
  • 12.7 Is there a link in each web page to avoid or quickly access the main content area (except in specific cases)?
  • 12.8 Is the order of tabulation consistent in each web page?
  • 13.3 Does every office document you download have an accessible version on each web page, except in specific cases?
  • 13.8 In each web page, can each item that is on or flashing be controlled by the user?
  • 13.10 Can the features that can be used or are available through a complex gesture also be available through a simple gesture in each web page (except in specific cases)?
     

Exceptions for disproportionate burden

No exceptions.

Content that is not subject to accessibility requirements

Files available in desktop formats published prior to September 23, 2018

 

PREPARATION OF THIS ACCESSIBILITY STATEMENT

This statement was issued on July 4, 2025.

Technologies used to build the website. 

  • HTML
  • CSS
  • JavaScript

Test environment

The web pages were tested using the following web browser and screen reader combinations:

  • Windows, NVDA 2024.4.1, Firefox 132
  • Windows, Jaws 2025, Firefox 132
  • macOS, VoiceOver, Safari
  • Native Android, TalkBack 15.1, Chrome
  • iOS, VoiceOver, Safari

The following tools were used during the evaluation:

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

Compliance verified site pages

  1. Home: https://france.ca-indosuez.com/
  2. Legal Information: https://france.ca-indosuez.com/pages/mentions-legales
  3. Contact: https://france.ca-indosuez.com/contact
  4. For one thing: https://france.ca-indosuez.com/a-la-une
  5. News: https://france.ca-indosuez.com/a-la-une/actualites
  6. News: https://france.ca-indosuez.com/a-la-une/actualites/indosuez-wealth-management-annonce-son-intention-d-acquerir-banque-thaler
  7. Trade Wars Episode II: https://france.ca-indosuez.com/a-la-une/expertises/guerres-commerciales-episode-ii
  8. Indosuez in France: https://france.ca-indosuez.com/indosuez-en-france
  9. Our commitments in France: https://france.ca-indosuez.com/indosuez-en-france/nos-engagements
  10. Our approach to compliance in France: https://france.ca-indosuez.com/indosuez-en-france/notre-approche-de-la-conformite


FEEDBACK AND CONTACT

If you are unable to access any content or service, you may contact our Technical Assistance team to be directed to an accessible alternative or obtain the content in another form.

CA Indosuez in France:


MEANS OF REDRESS

This procedure should be used in the following case.

You have notified the person responsible for the website of an accessibility defect that prevents you from accessing any content or services on the portal and you have not received a satisfactory response.

CA Indosuez France: