Accessibility

This accessibility statement applies to the Welcome website.

The Welcome website (https://welcome.businessfrance.fr/en) does not comply with the General Framework for Improving Accessibility (RGAA) version 4.1.2.
The details of the audit results are provided below.

The compliance audit carried out by Wavestone on June 3, 2026, on the production site revealed that 45% of the applicable criteria of RGAA version 4.1.2 were met.
This score corresponds to an Access-Score value of D.

List of non-compliant criteria
The 41 criteria that do not comply with the guidelines are:
1.1 – Does every image that conveys information have a text alternative?
1.2 – Are all decorative images correctly ignored by assistive technologies?
1.3 – For each image conveying information that has a text alternative, is this alternative relevant (except in special cases)?
1.6 – Does each image conveying information have, if necessary, a detailed description?
1.8 – Each text image conveying information, in the absence of a replacement mechanism, must, if possible, be replaced by styled text. Is this rule followed (except in special cases)?
1.9 – Is each image caption, if necessary, correctly linked to the corresponding image?
3.1 – On every web page, information must not be conveyed solely through color. Is this rule followed?
3.2 – On each web page, is the contrast between the text color and the background color sufficiently high (except in special cases)?
4.1 – Does each pre-recorded time-based media item have, where necessary, a text transcript or audio description (except in special cases)?
4.7 – Is each time-based media item clearly identifiable (except in special cases)?
4.8 – Does each non-time-based media item have, where necessary, an alternative (except in special cases)?
4.13 – Is every time-based and non-time-based media element compatible with assistive technologies (except in special cases)?
5.7 – For each data table, is the appropriate technique used to associate each cell with its headers (except in special cases)?
6.1 – Is every link explicit (except in special cases)?
7.1 – Is each script, where necessary, compatible with assistive technologies?
7.3 – Can each script be controlled using a keyboard and any pointing device (except in special cases)?
7.5 – On each web page, are status messages correctly rendered by assistive technologies?
8.2 – For each web page, is the generated source code valid according to the specified document type (except in special cases)?
8.6 – For each web page with a page title, is the title relevant?
8.7 – On each web page, is every language change indicated in the source code (except in special cases)?
8.8 – On each web page, is the language code for each language change valid and relevant?
8.9 – On each web page, tags must not be used solely for presentation purposes. Is this rule followed?
9.1 – On each web page, is the information structured through the appropriate use of headings?
9.2 – On each web page, is the document structure consistent (except in special cases)?
9.3 – On each web page, is every list properly structured?
10.1 – Are style sheets used on the website to control the presentation of information?
10.2 – On each web page, does the visible content that conveys information remain present when style sheets are disabled?
10.3 – On each web page, is the information still understandable when style sheets are disabled?
10.5 – On each web page, are CSS declarations for element background colors and fonts used correctly?
10.7 – On each web page, for each element receiving focus, is the focus indicator visible?
10.8 – For each web page, is hidden content intended to be ignored by assistive technologies?
10.9 – On each web page, information must not be conveyed solely by shape, size, or position. Is this rule followed?
10.10 – On every web page, information must not be conveyed solely through shape, size, or position. Is this rule implemented appropriately?
10.12 – On every web page, can the user redefine text spacing properties without losing content or functionality (except in special cases)?
10.13 – On every web page, can the user control additional content that appears when a user focuses on or hovers over an interface component (except in special cases)?
10.14 – On each web page, can additional content displayed solely through CSS styles be made visible using a keyboard and any pointing device?
11.5 – In each form, are fields of the same type grouped together, where necessary?
11.10 – In each form, is the input control used appropriately (except in special cases)?
12.6 – Can the content grouping areas present on multiple web pages (header, main navigation, main content, footer, and search engine areas) be accessed or skipped?
12.8 – On each web page, is the tab order consistent?
13.3 – On each web page, does every downloadable office document have an accessible version, if necessary (except in special cases)?

Technologies Used

The technologies used on the site are as follows:
1. HTML5
2. CSS
3. JavaScript (client-side and page-generation framework)

Test environment

Content rendering with assistive technologies was tested in accordance with the testing environment described in RGAA 4.1.2:
1. MS-Windows 11;
2. NVDA 2023;
3. Google Chrome.

Tools for auditing accessibility

The following tools were used to verify accessibility:
1. Web browser: Mozilla Firefox, Google Chrome;
2. Extensions:
A. Web Developer Toolbar;
B. RGAA Assistant;
C. HeadingsMap
D. WCAG Color Contrast Checker
3. NVDA 2023
4. O·C·A·A

1. Homepage
2. Process of setting up business
3. International schools
4. Foreign Investment in France
5. Company choice simulator
6. Support for your project
7. Corporate tax
8. News
9. A dynamic market
10. France’s economic position and key indicators

If you are unable to access any content or service, you can contact the site manager by clicking here, to be directed to an accessible alternative or to obtain the content in another form.

Under French law, this procedure is to be used in the following case: you have notified the website manager of a lack of accessibility that is preventing you from accessing content or one of the portal’s services and you have not received a satisfactory response.

You may:

• Write a message to the Human Rights Defender.
• Contact the Rights Defender delegate in your region.
• Send a letter by post (free of charge, do not put a stamp on it) to :
  Défenseur des droits
  Libre réponse 71120,
  75342 Paris Cedex 07.