Accessibility
Compliance status
This accessibility statement applies to the Welcome website.
The Welcome website (https://welcome.businessfrance.fr/en) is partially compliant with the General Framework for Improving Accessibility (RGAA), version 4.1.2.
Audit results
The compliance audit conducted by Wavestone on July 31, 2026, on the production website found that 55% of the applicable RGAA 4.1.2 criteria are met.
This score corresponds to an Access-Score value of D.
Non-compliant criteria
List of non-compliant criteria
The following 33 criteria of the RGAA framework were found to be non-compliant:
1. 1.1 – Does each informative image have a text alternative?
2. 1.2 – Is each decorative image properly ignored by assistive technologies?
3. 1.3 – For each informative image with a text alternative, is the alternative relevant (except in special cases)?
4. 1.6 – Does each informative image have a detailed description when necessary?
5. 1.8 – Where no replacement mechanism is available, is each image of text conveying information replaced with styled text whenever possible (except in special cases)?
6. 1.9 – Is each image caption properly associated with the corresponding image when necessary?
7. 3.2 – On each web page, is the contrast between text color and background color sufficiently high (except in special cases)?
8. 4.1 – Does each pre-recorded time-based media have a text transcript or audio description when necessary (except in special cases)?
9. 4.8 – Does each non-time-based media have an alternative when necessary (except in special cases)?
10. 4.13 – Is each time-based and non-time-based media compatible with assistive technologies (except in special cases)?
11. 6.1 – Is each link meaningful and clearly identified (except in special cases)?
12. 7.1 – Is each script compatible with assistive technologies when necessary?
13. 7.3 – Can each script be operated using a keyboard and any pointing device (except in special cases)?
14. 7.5 – On each web page, are status messages correctly conveyed by assistive technologies?
15. 8.2 – Is the generated source code valid according to the specified document type (except in special cases)?
16. 8.7 – Is every language change indicated in the source code on each web page (except in special cases)?
17. 8.9 – Are HTML elements not used solely for presentation purposes?
18. 9.1 – Is information structured through the appropriate use of headings on each web page?
19. 10.2 – Does visible informational content remain available when style sheets are disabled?
20. 10.3 – Does information remain understandable when style sheets are disabled?
21. 10.7 – Is keyboard focus visible for every element receiving focus?
22. 10.9 – Is information not conveyed solely through shape, size, or position?
23. 10.12 – Can text spacing properties be redefined by users without loss of content or functionality (except in special cases)?
24. 10.13 – Can additional content appearing when an interface component receives focus or is hovered over be controlled by the user (except in special cases)?
25. 10.14 – Can additional content displayed solely through CSS be made visible using a keyboard and any pointing device?
26. 11.1 – Does each form field have a label?
27. 11.2 – Is each form field label relevant (except in special cases)?
28. 11.5 – Are form fields of the same type grouped together when necessary?
29. 11.10 – Is input validation used appropriately in each form (except in special cases)?
30. 12.6 – Can recurring content regions (header, main navigation, main content, footer, and search functionality) be reached or bypassed?
31. 12.8 – Is the tab order consistent on each web page?
32. 12.9 – Does navigation avoid creating keyboard traps?
33. 13.3 – Does each downloadable office document have an accessible version when necessary (except in special cases)?
Drawing up this declaration of accessibility
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
Site pages used for compliance verification
Feedback and contact
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.
Recourse
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.