Proparco is committed to improving the accessibility of its internet, intranet, extranet and software packages (and mobile applications and urban digital displays) in accordance with Article 47 of Law No. 2005-102 of 11 February 2005.
AccessiWay agency supports Proparco in its digital accessibility efforts and implements the following strategy and actions:
- Multi-year accessibility plan for 2023-2024: in progress.
- 2023-2024 action plan: in progress.
The following accessibility statement was written on September 25, 2023, for the https://www.proparco.fr/fr website. It has been valid as of its publication date and must be updated after three years, in the event of major changes to the website, or 18 months after the release of a new version of the framework.
Compliance status
The https://www.proparco.fr/fr website has an accessibility rate of 54.29% and is therefore partially compliant with version 4 of the General Accessibility Improvement Framework (RGAA) due to the non-compliance and exceptions listed below.
Test results
The compliance audit carried out on September 25, 2023, by AccessiWay reveals that 54.29% of version 4 of the RGAA criteria have been met.
Results in detail:
- Number of criteria met: 38
- Number of non-compliant criteria: 32
- Number of inapplicable criteria: 36
Inaccessible content
Criteria:
- 1.2: Are all decorative images correctly ignored by assistive technologies?
- 1.3: Does each information-carrying image with a text alternative have an appropriate text alternative (except in special cases)?
- 1.4: For each image used as a CAPTCHA or as a test image, with a text alternative, does this alternative make it possible to identify the nature and function of the image?
- 1.5: For each image used as a CAPTCHA, is there an alternative access solution to the CAPTCHA content or function?
- 3.2: On each web page, is there sufficient contrast between the text color and background color (except in special cases)?
- 3.3: Are the colors used for the interface components or information-carrying graphic elements on each web page sufficiently contrasted (except in special cases)?
- 5.3: For each formatting table, is the linearized content still understandable?
- 5.6: For data tables, is each column header and row header marked correctly?
- 6.1: Is each link explicit (except in special cases)?
- 6.2: Does each link have a title on each web page?
- 7.1: Is each script compatible with assistive technologies, if necessary?
- 7.3: Can each script be controlled by the keyboard and any pointing device (except special cases)?
- 7.5: Do assistive technologies correctly interpret the status messages on each web page?
- 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: On each web page, is each language change indicated in the source code (except in special cases)?
- 8.9: On every web page, beacons must not be used solely for presentation purposes. Is this rule respected?
- 9.1: Is the information on each web page structured by the appropriate use of titles?
- 9.3: Is each list properly structured on each web page?
- 9.4: Is every quotation correctly indicated on every web page?
- 10.4: Is the text on each web page still readable when the font size is increased by at least 200% (excluding special cases)?
- 10.6: On each web page, is each link whose nature is not obvious visible in relation to the surrounding text?
- 10.7: On each web page, for each focused element, is the focus visible?
- 10.11: For each web page, can the content be presented without using both vertical scrolling for a window with a height of 256 px or horizontal scrolling for a window with a width of 320px (except special cases)?
- 11.1: Does each form field have a label?
- 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 in a relevant way (except in special cases)?
- 11.13: Can the purpose of an input field be inferred to facilitate the automatic filling of fields with user data?
- 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 tab order consistent on all web pages?
- 12.9: Navigation on the web pages must not contain any keyboard traps. Is this rule respected?
- 13.8: Is every moving or flashing piece of content on every web page controllable by the user?
Exemptions for disproportionate burden
No content to mention
Content not subject to the accessibility obligation
No content to mention
Issuance of this accessibility statement
This statement was issued on September 25, 2023.
Technologies used to produce the website
Test environment
Operating systems
- Apple Mac OS X 13.4
- Microsoft Windows 11
- Apple iOS 16
- Google Android 13
Browsers and software
In the latest versions available on the different operating systems:
- Google Chrome
- Windows Edge
- Safari
- Brave
- Adobe Acrobat Reader / Preview on Mac (for PDFs only)
Tools for assessing accessibility
- Emulation of the mouse, magnifiers and on-screen keyboards of the various systems.
- VoiceOver (Apple systems only)
- TalkBack (Android only)
- NVDA 2023 and Freedom scientific Jaws 2022 (PC systems only)
- Tanaguru webext RGAA4
- RGAA wizard
- Graphical assessment tools present on the various systems (for colors, contrasts, subtitles, etc.)
Web pages that have undergone the compliance check in French
