Accessibility

Mobilize FS is non-compliant with the European standard EN 301549. The non-compliances are listed below. 

The compliance audit against RAWEB 1.0, conducted by the company Temesis, reveals that : 

• 49.28% of the RAWEB criteria are met.

In detail : 

• Number of compliant criteria : 34 
• Number of non-compliant criteria : 35 
• Number of non-applicable criteria : 67

The content does not comply with the criteria listed below: 

Non-compliance 

List of non-compliant criteria: 

• 1.2 Is each decorative image correctly ignored by assistive technologies ? 
• 1.3 For each informative image with a text alternative, is this alternative relevant (excluding special cases) ? 
• 1.8 Should each informative text image, in the absence of a replacement mechanism, be replaced by styled text if possible? Is this rule respected (excluding special cases) ? 
• 3.2 On each web page, is the contrast between the text color and its background color sufficiently high (excluding special cases) ? 
• 5.3 For each layout table, does the linearized content remain understandable ? 
• 5.4 For each data table with a title, is the title correctly associated with the data table ? 
• 5.6 For each data table, is each column header and row header correctly declared ? 
• 5.7 For each data table, is the appropriate technique used to associate each cell with its headers (excluding special cases) ? 
• 5.8 Layout tables must not use elements specific to data tables. Is this rule respected ? 
• 6.1 Is each link explicit (excluding special cases) ? 
• 7.1 Is each script, if necessary, compatible with assistive technologies ? 
• 7.3 Is each script controllable by the keyboard and by any pointing device (excluding special cases) ? 
• 7.4 For each script that initiates a change of context, is the user notified or do they have control over it ? 
• 7.5 On each web page, are status messages correctly rendered by assistive technologies ? 
• 8.6 For each web page with a page title, is this title relevant ? 
• 8.7 On each web page, is each language change indicated in the source code (excluding special cases) ? 
• 8.9 On each web page, tags must not be used solely for presentation purposes. Is this rule respected ? 
• 9.1 On each web page, is information structured through the appropriate use of headings ? 
• 9.3 On each web page, is each list correctly structured ? 
• 9.4 On each web page, is each quotation correctly indicated ? 
• 10.2 On each web page, does visible informative content remain present when style sheets are disabled ? 
• 10.3 On each web page, does information remain understandable when style sheets are disabled ? 
• 10.7 On each web page, for each element receiving focus, is the focus indicator visible ? 
• 10.9 On each web page, information must not be conveyed solely by shape, size, or position. Is this rule respected ? 
• 10.11 For each web page, can content be presented without loss of information or functionality and without requiring either vertical scrolling for a window with a height of 256 px, or horizontal scrolling for a window with a width of 320 px (excluding special cases) ? 
• 10.12 On each web page, can text spacing properties be redefined by the user without loss of content or functionality (excluding special cases) ? 
• 11.2 Is each label associated with a form field relevant (excluding special cases) ? 
• 11.9 In each form, is the label of each button relevant (excluding special cases) ? 
• 11.10 In each form, is input validation used in a relevant manner (excluding special cases) ? 
• 12.6 Can content grouping areas present on multiple web pages (header, main navigation, main content, footer, and search engine areas) be reached or bypassed ? 
• 12.8 On each web page, is the tab order logical ? 
• 13.3 On each web page, does each downloadable office document have an accessible version, if necessary (excluding special cases) ? 
• 14.1 Does the website documentation describe the available accessibility features and information regarding accessibility compatibility ? 
• 14.3 Is the website documentation accessible ? 
• 16.3 Is the documentation provided by the support service accessible ?

Derogation for Disproportionate Burden 

None. 

Content Exempt from the Accessibility Obligation

• Files available in office formats published before September 23, 2018
• Third-party content that is neither funded nor developed by the concerned organization and is not under its control : Leaflet Map

This statement was prepared on March 16, 2026.

• CMS Drupal
• HTML5
• CSS
• Javascript

The web page tests were performed using the following combinations of web browsers and screen readers : 

• Windows, NVDA 2025.3.3, Firefox 148.0.2 
• Windows, Jaws 2025, Firefox 148.0.2 
• macOS, VoiceOver, Safari 
• Native Android, TalkBack 15.1, Chrome 
• iOS, VoiceOver, Safari

• WCAG contrast checker 
• HeadingsMap 
• Web developer 
• ARC Toolkit

• Home page 
• Contact page 
• "Sitemap" page 
• "Legal Notice" page 
• "Accessibility" page 
• News list page 
• "Finance" page 
• "Financial Ratings" page 
• "Join Us" page 
• "Our Job Offers" page 
• "Our Customers" page 
• "Financing for Individuals" page 
• "Governance" page 
• "Martin Thomas" page 
• "Our Locations" page

If you are unable to access any content or service, you may contact the website manager by email atweb-accessibility@mobilize-fs.com to be directed to an accessible alternative or to obtain the content in another format.

This procedure is to be used in the following case: You have reported an accessibility defect to the website manager that prevents you from accessing content or one of the portal's services, and you have not received a satisfactory response. 

• Write a message to the Defender of Rights (Défenseur des droits) : https://www.defenseurdesdroits.fr/fr/contact 
• Contact the Defender of Rights delegate in your region : https://www.defenseurdesdroits.fr/saisir/delegues 

• Send a letter by post (free of charge within France, no stamp required) to the following address :

  Défenseur des droits 
  Libre réponse 71120 
  75342 Paris CEDEX 07 
  France