ACCESSIBILITY DECLARATION

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. The 2020-2022 Multi-Year Accessibility Plan as well as the 2020-2021 Action Plan are currently being drafted and will be published shortly. The 2020-2022 Multi-Year Accessibility Plan as well as the 2020-2021 Action Plan are currently being drafted and will be published shortly.

1.1 STATE OF COMPLIANCE

The BNP Paribas Group (https://group.bnpparibas) is in partial compliance with the General Guidelines for Improving Accessibility (“RGAA”), version 4.0, due to the non-conformities and deviations listed below.

1.2 DRAWING UP THIS ACCESSIBILITY DECLARATION

This declaration was drawn up on 01/10/2020.

1.3 RESULTS OF THE TESTS

The audit of compliance performed in-house indicates 53% compliance with the RGAA version 4.0 criteria.

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

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

  • 42 criteria in compliance
  • 34 criteria not in compliance

1.4 INACCESSIBLE CONTENT

  • 1.1 Does each image conveying information have a textual alternative?

Some images don’t convey information and have an irrelevant textual alternative. Not very visible on the site, but nevertheless present.

  • 1.2 Is each decorative image correctly ignored by the assistive technologies?

This problem is more common, as the decorative images are not ignored by the assistive technologies.

  • 1.3 For each image conveying information that has a textual alternative, is this alternative relevant (except in special cases)?

In one case on the site the textual alternative is not relevant.

  • 1.3 For each image used as a CAPTCHA or as a test image, having a textual alternative, does this alternative permit identification of the nature and function of the image?

In one case on the site the textual alternative is not relevant.

  • 3.1 The information must not be given solely by the colour on any web site.  Is this rule respected?

Some information such as breadcrumbs and categories are only indicated by a change of colour upon hovering.

  • 3.2 Is the contrast between the colour of the text and the colour of the background sufficiently sharp on every web page (excluding special cases)?

The contrast between the colour of the text and the colour of its background is not sharp enough.

  • 3.3 On each web page, is there sufficient contrast between the colours used in the interface components or the graphical elements conveying information (except in special cases)?

The green colour used in the interface components is not accessible.

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

The data tables do not have cells associated with headers. The <th> tag should use the "id", "scope", "role=rowheader" or "column-header" attributes.

  • 6.1 Is each link explicit (except in special cases)?

On the home page, the articles have three links in a set, which is problematic for the speech synthesis.

  • 6.2 On each web page, does every link, with the exception of the anchors, have a title?

On several pages of the site, a title is missing between <a> and </a>.

  • 7.1 Is every script, whenever necessary, compatible with assistive technologies?

Some elements of the site are not vocalized, such as the timeline news page.

  • 7.3 Can every script be controlled by the keyboard and by any pointing device (except in special cases)?

Keyboard navigation is not possible on the whole site. On the Spokespeople page, you can open someone’s file but you can't use the Escape key or the “X” to leave the window, which is inaccessible.

  • 7.4 For each script that initiates a context change, is the user warned or do they have control over this?

When performing a search on the news page, the number of results found is not returned to the user. There is no control over the creation of email alerts on the job offers page.

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

The status messages are not returned correctly, for example the absence of articles during a search for articles.

  • 8.7 Is each language change indicated in the source code on every web page (except in special cases)?

The language changes are not specified in the source code, which results in poor vocalization.

  • 9.1 Is the information structured by the use of appropriate headers on every web page?

Headers have been skipped on several pages on the site. The result of this error is the skip from header <h2> to <h4> as can be seen on the Jobs and Careers page.

  • 9.2 Is the structure of the document coherent on every web page (except in special cases)?

The structure of the source code is not respected on the site. The <main> is not present on all pages. It is hidden under a <div>.

  • 10.6 In each web page, is every link whose nature is not obvious visible in relation to the surrounding text?

In the citations block on the news page, there exists a link in the same colour as the text.

  • 10.7 Is the focus indicator visible for every element receiving a focus on every web page?

The pictograms in the header only change colour, which does not validate this criterion. Other elements such as the “Reset" button on the "All News Stories" page do not have a visible focus indicator.

  • 10.8 Is hidden content designed to be ignored by the assistive technologies on every web page?

On the newsletter subscription page, the radio button is in display none.

  • 10.14 Can additional content appearing only via CSS styles be made visible using the keyboard and any pointing device on every web page?

On the Media Room page, the pictogram for More Details and Downloading the Media Library is visible only when navigating with the mouse. The block disappears upon keyboard navigation. 

  • 11.4 In each form, are all the field labels and their associated fields associated (except in special cases)?

On the Legal Notice page, when I try to share the article by email, it can be seen that the field labels and their associated field are not joined.

  • 11.10 In each form, is the input requirement indicated in a relevant way (except in special cases)?

In the fields for the forms for newsletter subscriptions sharing the Legal Notices page by email, the mandatory fields are not indicated, or they are not indicated above the fields in question.

  • 11.11 In each form, is the input requirement accompanied, whenever necessary, by suggestions to facilitate the correction of input errors?

An error is indicated in the field, but there are no suggestions to facilitate error correction.

  • 12.11 In each web page, is any additional content that appears when hovering, focusing or activating an interface component reachable, whenever necessary, with the keyboard?

In the Spokespeople page, the "Close" button cannot be accessed when opening a biography.

  • 13.3 In each web page, does each office document available for downloading have, whenever necessary, an accessible version (except in special cases)?

Not all the PDF documents on the site are accessible. The 2019 integrated report is not accessible; the document is not tagged. Documents dated before 23 September 2018 are exempt, but this one is dated 02/06/2020.

1.5 DRAWING UP THIS ACCESSIBILITY DECLARATION

1.5.1 Technologies used for the production of group.bnpparibas

  • HTML5
  • CSS
  • Javascript

1.5.2 Test environment 

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

  • Chrome 85 and NVDA 2020.1
  • Firefox and NVDA 2020.1
  • VoiceOver on iOS X

1.5.3 Tools for evaluating accessibility

  • Contrast Colour Analyser
  • Chrome development tool
  • Web Developer Toolbar (Chrome extension)

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 BNP Paribas Group site manager to be directed to an accessible alternative or to obtain the content in another form.

To do this, send a message to: 


1.7 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