Digital accessibility

Agence Française de Développement (AFD) promotes inclusion and diversity, and has therefore established a continuous improvement process to make sure its afd.fr website is accessible, especially for people with disabilities.
This page presents the accessibility policy for the afd.fr website and the general level of accessibility observed, according to the relevant standards and regulations.
  • logo linkedin
  • logo email
computer, digital: accessibility statement of the site afd.fr
© Backdrop Ltd/Proparco

Why does digital accessibility matter?

An accessible website is one that allows people with disabilities to access and use its content and features easily. Digital accessibility promotes inclusion and diversity by ensuring that no one is excluded from accessing online information and services.

The digital accessibility obligation applies to government services, local authorities, public institutions, organizations entrusted with a public service mission, companies with a turnover in France exceeding 250 million euros, and non-profit organizations.

AFD has introduced a continuous improvement process to provide users with the best possible experience and to comply with the General Accessibility Improvement Framework (RGAA), with the aim of making the afd.fr website more accessible. 

Accessibility statement

AFD 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 AFD 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.afd.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.afd.fr/fr website has an accessibility rate of 50.68% 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 50.68% of version 4 of the RGAA criteria have been met.

Results in detail:

  • Number of criteria met: 37
  • Number of non-compliant criteria: 36
  • Number of inapplicable criteria: 33
     
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.6: Does each information-carrying image have a detailed description, if necessary?
  • 1.8: If no replacement mechanisms are used, each information-carrying text image should be replaced by styled text if possible. Is this rule respected (except in special cases)?
  • 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)?
  • 4.1: Does all prerecorded time-based media have a text transcript or audio description, if necessary (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.3: Is the default language present on each web page?
  • 8.5: Does every web page have a page title?
  • 8.7: On each web page, is each language change indicated in the source code (except in special cases)?
  • 9.1: Is the information on each web page structured by the appropriate use of titles?
  • 9.2: Is the document structure consistent on each web page (except in special cases)?
  • 9.3: Is each list properly structured on each web page?
  • 10.1: Are the style sheets used to control the presentation of information on the website?
  • 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)?
  • 10.13: On each web page, is the additional content which appears when focusing on or hovering over an interface component controllable by the user (except in special cases)?
  • 11.1: Does each form field have a label?
  • 11.10: In each form, is the input control used in a relevant way (except in special cases)?
  • 11.11: In each form, is the input control combined with suggestions to facilitate the correction of input errors, if necessary?
  • 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?
  • 12.11: On each web page, is the additional content which appears when focusing on, hovering over or activating an interface component accessible using the keyboard if necessary?
     
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
  • HTML5
  • CSS
  • JavaScript
     
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

Feedback and contact

If you are unable to access any of the content or services, please contact the responsible person at Agence Française de Développement to obtain an accessible alternative or receive the content in another form.

Contact us
 
Remedies

If you experience a lack of accessibility preventing you from accessing any of the website content or features and do not receive a response from us after reporting it, you have the right to send your complaints or a request for referral to the Defender of Rights.

There are several ways to do this: