BNP Paribas undertakes to make its internet, intranet and extranet sites and software packages accessible in accordance with Article 47 of Law no. 2005-102 of 11 February 2005.

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

  • Multi-year accessibility plan is currently being drafted
  • Actions will be planned shortly
  • Action plan is currently being drafted

This accessibility statement applies to the site

1.1 State of compliance

BNP Paribas INVEST ( is in partial compliance with the General Guidelines for Improving Accessibility (“RGAA”), version 4.1, due to the non-conformities and deviations listed below.

1.2 State of accessibility declaration

This accessibility statement was drawn up on 01.12.2022.

1.3 Results of the tests

The audit of compliance performed internally indicates 43% compliance with the RGAA version 4.1 criteria.

The average rate of compliance of the online service is 74%.

Out of the 106 criteria, 67 are applicable, of which:

  • 29 criteria in compliance
  • 38 criteria not in compliance
  • 39 criteria are non applicable

1.4 Non-accessible content

1.1 Does each image carrying information have a textual alternative?

Presence of action buttons in SVG format without alternatives text.

1.6 Does each information-bearing image, if necessary, have a detailed description?

Presence of complex graphs without detailed descriptions.

3.1 In each Web page, information should not be given solely by colour. Is this rule respected?

In some graphs information such as the active tab is given only by colour.

3.2 In each web page, is the contrast between the colour of the text and the colour of its background sufficiently high (excluding special cases)?

Some text colours are not sufficiently contrasted.
Information transmitted only by colour.

3.3 In each web page, are the colours used in the interface components or graphic elements that carry information sufficiently contrasted (except in special cases)?

Certain colours of interface or graphic elements are not sufficiently contrasted.

5.4 For each data table with a title, is the title correctly associated with the data table?

No title on the tables.

5.6 Are each column heading and line heading correctly reported for each data table?

Presence of unidentified empty cells.

5.7 For each data table, is the appropriate technique for associating each cell with its headers used (excluding special cases)?

No indication on column and line headers

7.1 Is each script, if compulsory, compatible with assistive technologies?

You can't leave the sub menu with the ESC key.
A textual alternative in the wrong language.
Tab not accessible on graphics.

7.3 Is each script controllable by the keyboard and any pointing device (excluding special cases)?

Thematic filtering not available at the keyboard on financial reports.

7.5 Are status messages correctly returned by assistive technologies on each web page?

No status role on the display of filtering results.

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

Error in source code grammar.

10.2 In each Web page, does visible information-bearing content remain present when style sheets are deactivated?

Presence of presentation attributes.

10.5 On each Web page, are element-based and font-based CSS statements properly used?

No background colour.

10.7 On each Web page, for each focus element, is focus visible?

Lack of visibility of spotlight.

11.2 Is each label associated with a form field relevant (excluding specific cases)?

No visible label.

11.9 In each form, is the name of each button relevant (except in special cases)?

Some button headings are not sufficiently relevant.

11.10 Is the input control used appropriately in each form (excluding special cases)?

No concept of compulsory fields.
Inexplicit error message that cannot guide the user.

11.11 In each form, is there any suggestions for correcting input errors, if possible?

The forms do not include input help to guide the user during the input.

11.13 Can the purpose of a capture field be deduced to facilitate the automatic filling of fields with the user’s data?

No auto complete attribute on the form fields requiring it.

12.6 Can the content aggregation zones present in several web pages (header, main navigation, main content, footer and search engine zones) be reached or avoided?

No easy role which enables to identify areas.

12.7 In each web page, is there an avoidance link or quick access to the main content area (excluding special cases)?

No avoidance link on site.

12.8 Is the tabulation order consistent in each web page?

The tabulation order is not consistent on some pages of the site.

13.3 Does each downloaded office document have an accessible version (except in special cases) on each web page?

Not all PDF documents on the site are accessible.

13.10 In each web page, can features that can be used or made available by means of a complex gesture also be made available by means of a simple gesture (except in special cases)?

Sliding not accessible on some graphics.

1.5 Drawing up the accessibility declaration

1.5.1 Technologies used for the production of

  • HTML5
  • CSS
  • Javascript

1.5.2 Test Environnement

The verifications of content retrieval were performed using the RGAA 4.1 guidelines, with the following versions:

  • Firefox 104.0.1
  • NVDA 2020.1
  • JAWS 2020
  • VoiceOver sous iOS X

1.5.3 Tools for evaluating accessibility

  • Contrast Color Analyser
  • Heading Maps
  • Assistant RGAA V4.1
  • Development Tool
  • Web Developer Toolbar

1.5.4 Site pages covered by the verification of compliance

1.6 Feedback and contact

If you are unable to access any content or service, you may contact the Invest BNP Paribas site manager to be directed to an accessible alternative or to obtain the content in another form.

To do this, send a message to: investor.relations [at] bnpparibas (dot) com

4. Remedies

This procedure is to be used in the following case: You have reported to the website manager a lack of accessibility that prevents you from accessing any of the portal’s content or services and you have not received a satisfactory response