This statement was drafted on 21/08/2025 for the website
https://www.motoblouz.com/.
It is valid from its publication, must be updated after 3 years, following major changes to the site, or 18 months after a new version of the reference framework.
Motoblouz is committed to making its websites, mobile applications, intranet, extranet, and software accessible in accordance with Article 47 of Law No. 2005-102 of 11 February 2005.
We value inclusion and diversity, and we ensure that our website:
https://www.motoblouz.com/ is accessible to everyone, especially to people with disabilities.
In this digital accessibility approach, we collaborate with
Accessiway.
We are firmly committed to a web for all. We aspire, with a long-term and responsible vision, to fully meet regulatory requirements, notably
RGAA 4.1.2 and the European standard
EN 301 549.
The website:
https://www.motoblouz.com/ has an accessibility rate of 47.22% and is therefore
Non-compliant with the general reference for improving accessibility (RGAA 4.1.2).
The contents listed below are not accessible for the following reasons.
Non-compliance
- 1.2: Is each decorative image correctly ignored by assistive technologies?
- 1.3: For each informative image with a textual alternative, is this alternative relevant (excluding special cases)?
- 1.8: Each text image carrying information, in the absence of a replacement mechanism, must if possible be replaced by styled text. Is this rule respected (excluding special cases)?
- 3.1: On each web page, information must not be provided solely by color. Is this rule respected?
- 3.2: On each web page, is the contrast between the text color and its background color sufficiently high (excluding special cases)?
- 3.3: On each web page, are the colors used in interface components or graphical elements carrying information sufficiently contrasted (excluding special cases)?
- 4.1: Does each pre-recorded time-based media have, if necessary, a textual transcript or audio description (excluding special cases)?
- 4.5: Does each pre-recorded time-based media have, if necessary, a synchronized audio description (excluding special cases)?
- 4.7: Is each time-based media clearly identifiable (excluding special cases)?
- 5.4: For each data table with a title, is the title correctly associated with the data table?
- 5.6: For each data table, are each column header and each 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)?
- 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 keyboard and any pointing device (excluding special cases)?
- 7.4: For each script that initiates a change of context, is the user warned or in control?
- 7.5: On each web page, are status messages correctly conveyed by assistive technologies?
- 8.5: Does each web page have a page title?
- 8.7: On each web page, is each language change indicated in the source code (excluding special cases)?
- 9.1: On each web page, is the information structured by the appropriate use of headings?
- 9.2: On each web page, is the document structure coherent (excluding special cases)?
- 9.3: On each web page, is each list correctly structured?
- 10.1: On the website, are style sheets used to control the presentation of information?
- 10.4: On each web page, is the text still readable when the font size is increased to at least 200% (excluding special cases)?
- 10.6: On each web page, is each link whose nature is not obvious visible compared to the surrounding text?
- 10.7: On each web page, for each element receiving focus, is the focus indication visible?
- 10.8: For each web page, are hidden contents intended to be ignored by assistive technologies?
- 10.11: For each web page, can contents be presented without resorting to both vertical scrolling for a window with a height of 256px or horizontal scrolling for a window with a width of 320px (excluding special cases)?
- 10.13: On each web page, are additional contents appearing on focus or hover of an interface component controllable by the user (excluding special cases)?
- 10.14: On each web page, can additional contents appearing via CSS styles only be made visible by keyboard and any pointing device?
- 11.1: Does each form field have a label?
- 11.5: In each form, are fields of the same nature grouped together, if necessary?
- 11.10: In each form, is input control used appropriately (excluding special cases)?
- 11.11: In each form, is input control accompanied, if necessary, by suggestions facilitating the correction of input errors?
- 11.13: Can the purpose of an input field be deduced to facilitate the autofilling of fields with user data?
- 12.7: On each web page, is there a skip link or quick access to the main content area present (excluding special cases)?
- 12.8: On each web page, is the tab order consistent?
- 13.8: On each web page, is each moving or blinking content controllable by the user?
Disproportionate Burden Exceptions
No content to mention
Contents not subject to the accessibility obligation
No content to mention
This statement was established on 21/08/2025.
If you are unable to access content or a service, you can contact the accessibility manager of
Motoblouz for guidance towards an accessible alternative or to obtain the content in another form.