{"id":272,"date":"2025-07-30T11:34:32","date_gmt":"2025-07-30T09:34:32","guid":{"rendered":"https:\/\/world.businessfrance.fr\/portal\/?page_id=272"},"modified":"2026-02-12T11:25:01","modified_gmt":"2026-02-12T10:25:01","slug":"digital-accessibility-statement","status":"publish","type":"page","link":"https:\/\/world.businessfrance.fr\/portal\/digital-accessibility-statement\/","title":{"rendered":"Digital Accessibility Statement"},"content":{"rendered":"\n
\n

Digital Accessibility Statement<\/h1>\n\n\n\n\n
\n

Compliance status<\/h2>\n\n\n\n

This accessibility declaration applies to the World Business France<\/strong> website .<\/p>\n\n\n\n

The World Business France<\/strong> website (https:\/\/world.businessfrance.fr\/portal\/<\/a>) is not compliant with the General Accessibility Improvement Framework (RGAA) version 4.1.2. The details of the audit results are provided below.<\/p>\n\n\n\n

Test results<\/h2>\n\n\n\n

The compliance audit carried out by Wavestone SA from December 15, 2025, to December 22, 2025, on the production website shows that 44% of the applicable criteria of RGAA version 4.1.2 are met. This score corresponds to an Access-Score value of D.<\/p>\n\n\n\n


Non\u2011compliant Criteria<\/h2>\n\n\n\n

List of non\u2011compliant criteria<\/strong>
The 35 criteria that do not comply with the framework are:<\/p>\n\n\n\n

1.1.2 \u2013 Is each decorative image properly ignored by assistive technologies?
2.1.3 \u2013 For each information\u2011carrying image that has a text alternative, is this alternative relevant (except in specific cases)?
3.3.2 \u2013 On each web page, is the contrast between the text color and its background color sufficiently high (except in specific cases)?
4.3.3 \u2013 On each web page, are the colors used in interface components or graphic elements that convey information sufficiently contrasted (except in specific cases)?
5.5.6 \u2013 For each data table, are all column headers and row headers properly marked up?
6.5.7 \u2013 For each data table, is the appropriate technique used to associate each cell with its headers (except in specific cases)?
7.6.1 \u2013 Is each link explicit (except in specific cases)?
8.6.2 \u2013 On each web page, does each link have a label?
9.7.1 \u2013 Is each script, when necessary, compatible with assistive technologies?
10.7.5 \u2013 On each web page, are status messages correctly conveyed by assistive technologies?
11.8.2 \u2013 For each web page, is the generated source code valid according to the specified document type (except in specific cases)?
12.8.6 \u2013 For each web page with a page title, is this title relevant?
13.8.7 \u2013 On each web page, is every language change indicated in the source code (except in specific cases)?
14.8.9 \u2013 On each web page, are tags not used solely for presentation purposes?
15.9.1 \u2013 On each web page, is information structured through the appropriate use of headings?
16.9.2 \u2013 On each web page, is the document structure coherent (except in specific cases)?
17.9.3 \u2013 On each web page, is every list properly structured?
18.10.2 \u2013 On each web page, does visible content conveying information remain available when style sheets are disabled?
19.10.3 \u2013 On each web page, does information remain understandable when style sheets are disabled?
20.10.7 \u2013 On each web page, for every element receiving focus, is the focus indicator visible?
21.10.8 \u2013 For each web page, are hidden contents meant to be ignored by assistive technologies?
22.10.9 \u2013 On each page, is information not conveyed solely by shape, size, or position?
23.10.10 \u2013 On each web page, is the rule stating that information must not rely solely on shape, size, or position implemented appropriately?
24.10.13 \u2013 On each web page, are additional contents that appear when an interface component receives focus or is hovered over user\u2011controllable (except in specific cases)?
25.10.14 \u2013 On each web page, can additional contents that appear only through CSS styles be made visible via keyboard and any pointing device?
26.11.1 \u2013 Does each form field have a label?
27.11.2 \u2013 Is each label associated with a form field relevant (except in specific cases)?
28.11.3 \u2013 In each form, are labels for fields with the same function and repeated several times on a page or across multiple pages consistent?
29.11.5 \u2013 In each form, are fields of the same nature grouped together when necessary?
30.11.10 \u2013 In each form, is input control used appropriately (except in specific cases)?
31.11.11 \u2013 In each form, when necessary, is input control accompanied by suggestions to help correct input errors?
32.11.13 \u2013 Can the purpose of an input field be inferred to facilitate autofill with the user\u2019s data?
33.12.1 \u2013 Does each set of pages provide at least two different navigation systems (except in specific cases)?
34.12.8 \u2013 On each web page, is the tab order coherent?
35.13.10 \u2013 On each web page, are functions usable or available by means of a complex gesture also available through a simple gesture (except in specific cases)?<\/p>\n\n\n\n

Preparation of this Accessibility Statement<\/h2>\n\n\n\n

Technologies Used<\/h3>\n\n\n\n

The following technologies were used on the site:
1. HTML5
2. CSS
3. JavaScript (client-side and page\u2011generation framework)<\/p>\n\n\n\n

Test Environment<\/h3>\n\n\n\n

Content rendering with assistive technologies was tested in accordance with the RGAA 4.1.2 test environment:<\/p>\n\n\n\n

    \n
  1. MS\u2011Windows 11<\/li>\n\n\n\n
  2. NVDA 202<\/li>\n\n\n\n
  3. Google Chrome<\/li>\n<\/ol>\n\n\n\n

    Tools Used to Assess Accessibility<\/h3>\n\n\n\n

    The following tools were used to verify accessibility:<\/p>\n\n\n\n

      \n
    1. Web browsers: Mozilla Firefox, Google Chrome<\/li>\n\n\n\n
    2. Extensions:
      A. Web Developer Toolbar
      B. RGAA Assistant
      C. HeadingsMap
      D. WCAG Color Contrast Checker<\/li>\n\n\n\n
    3. NVDA 2023
      <\/li>\n\n\n\n
    4. O\u00b7C\u00b7A\u00b7A<\/li>\n<\/ol>\n\n\n\n

      Pages Used for the Compliance Audit<\/h3>\n\n\n\n
        \n
      1. Homepage<\/a><\/li>\n\n\n\n
      2. Homepage Amlat<\/a><\/li>\n\n\n\n
      3. Escribirnos<\/a> <\/li>\n\n\n\n
      4. Events Archive <\/a><\/li>\n\n\n\n
      5. VivaTech <\/a><\/li>\n\n\n\n
      6. Comercio con Francia <\/a><\/li>\n\n\n\n
      7. Personal Data<\/a><\/li>\n<\/ol>\n\n\n\n

        Feedback and contact<\/h2>\n\n\n\n

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

        Recourse<\/h2>\n\n\n\n

        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.<\/p>\n\n\n\n

        You may:<\/p>\n\n\n\n