Accessibility
Declaration of conformity
eMundus is committed to making its website accessible in accordance with Article 47 of Law No. 2005-102 of 11 February 2005.
To this end, eMundus implements strategy and actions defined in this page.
This accessibility statement applies to the website of ME3-4S : https://me3-4sapply.imt-atlantique.fr/
Statement of compliance
The website ME3-4S does not comply with the General Accessibility Improvement Framework (RGAA) [RGAA 4.1.2 / to be confirmed]. The compliance status is determined by the overall compliance rate, which stands at 22.41 % (the average rate is 49.2 %). The 50 % target applies to the overall rate; as the platform is below this threshold, it is currently considered non-compliant, due to the non-compliances and exemptions listed below.
Test results
The product compliance audit, conducted on 19 May 2026, reveals an overall compliance rate of 22.41 % (the average rate is 49.2 %). Since this audit, some of the non-compliant criteria have been corrected:
- 28 of the 45 criteria listed below have been processed and integrated into the platform.
- The remaining 17 criteria are planned or in progress: 15 to do, 1 in progress (criterion 10.9) and 1 to be specified (criterion 9.2).
Details of the corrections to be applied
Drawn up following the audit and updated on 28 September 2026, this list specifies, for each correction, the associated RGAA criterion, its theme, its description, an estimate of the intervention time and its progress status. This list evolves over time and is completed as new needs are identified.
Status legend
- Corrected Correction applied and integrated into the platform.
- In progress Correction currently being processed.
- To do Correction identified, not yet started.
- To be specified Correction to be clarified before processing.
Images
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 1.1 | Does each image conveying information have a text alternative? | To do | T1 2027 | ||
| 1.4 | For each image used as a CAPTCHA or as a test image that has a text alternative, does this alternative make it possible to identify the nature and function of the image? | Corrected | - | ||
| 1.5 | For each image used as a CAPTCHA, is an alternative means of accessing the content or function of the CAPTCHA provided? | To do | T4 2026 | ||
Frames
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 2.1 | Does each frame have a frame title? | Corrected | - | ||
Colours
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 3.1 | On each web page, information must not be conveyed by colour alone. Is this rule respected? | Corrected | - | ||
| 3.2 | On each web page, is the contrast between the text colour and its background colour high enough (except in special cases)? | Corrected | - | ||
| 3.3 | On each web page, are the colours used in interface components or graphic elements conveying information sufficiently contrasted (except in special cases)? | Corrected | - | ||
Tables
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 5.3 | For each layout table, does the linearised content remain understandable (except in special cases)? | Corrected | - | ||
| 5.4 | For each data table with a title, is the title correctly associated with the data table? | Corrected | - | ||
| 5.6 | For each data table, are each column header and each row header correctly declared? | Corrected | - | ||
Links
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 6.1 | Is each link explicit (except in special cases)? | Corrected | - | ||
| 6.2 | On each web page, does each link, except anchors, have a label? | Corrected | - | ||
Scripts
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 7.1 | Is each script, where necessary, compatible with assistive technologies? | To do | T2 2027 | ||
| 7.3 | Is each script controllable by keyboard and by any pointing device (except in special cases)? | To do | T1 2027 | ||
| 7.5 | On each web page, are status messages correctly conveyed by assistive technologies? | To do | T4 2026 | ||
Mandatory elements
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 8.2 | For each web page, is the generated source code valid according to the specified document type (except in special cases)? | To do | T3 2027 | ||
| 8.6 | For each web page with a page title, is this title relevant? | To do | T1 2027 | ||
| 8.7 | On each web page, is each change of language indicated in the source code (except in special cases)? | Corrected | - | ||
| 8.9 | On each web page, tags must not be used solely for presentation purposes. Is this rule respected? | Corrected | - | ||
Information structure
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 9.1 | On each web page, is information structured through the appropriate use of headings? | Corrected | - | ||
| 9.2 | On each web page, is the document structure consistent (except in special cases)? | To be specified | - | ||
| 9.3 | On each web page, is each list correctly structured? | In progress | T4 2026 | ||
Information presentation
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 10.3 | On each web page, does information remain understandable when style sheets are disabled? | Corrected | - | ||
| 10.4 | On each web page, does the text remain legible when the character size is increased up to at least 200 %% (except in special cases)? | Corrected | - | ||
| 10.5 | On each web page, are the CSS declarations for element background and font colours used correctly? | Corrected | - | ||
| 10.6 | On each web page, is each link whose nature is not obvious visible relative to the surrounding text? | Corrected | - | ||
| 10.7 | On each web page, for each element receiving focus, is the focus visible? | Corrected | - | ||
| 10.8 | For each web page, are hidden contents intended to be ignored by assistive technologies? | Corrected | - | ||
| 10.9 | On each web page, information must not be conveyed solely by shape, size or position. Is this rule respected? | Corrected | - | ||
| 10.10 | On each web page, information must not be conveyed by shape, size or position alone. Is this rule implemented appropriately? | Corrected | - | ||
| 10.11 | For each web page, can the content be presented without loss of information or functionality and without requiring either vertical scrolling for a window 256 px high or horizontal scrolling for a window 320 px wide (except in special cases)? | To do | T3 2027 | ||
| 10.12 | On each web page, can the text spacing properties be redefined by the user without loss of content or functionality (except in special cases)? | To do | T1 2027 | ||
Forms
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 11.1 | Does each form field have a label? | To do | T1 2027 | ||
| 11.2 | Is each label associated with a form field relevant (except in special cases)? | Corrected | - | ||
| 11.5 | In each form, are fields of the same nature grouped together where necessary? | Corrected | - | ||
| 11.6 | In each form, does each grouping of form fields have a legend? | Corrected | - | ||
| 11.9 | In each form, is the label of each button relevant (except in special cases)? | Corrected | - | ||
| 11.10 | In each form, is input control used appropriately (except in special cases)? | To do | T2 2027 | ||
| 11.13 | Can the purpose of an input field be determined to facilitate the automatic filling of fields with the user's data? | Corrected | - | ||
Navigation
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 12.1 | Does each set of pages have at least two different navigation systems (except in special cases)? | To do | T2 2027 | ||
| 12.6 | Can the content grouping areas present on several web pages (header, main navigation, main content, footer and search engine areas) be reached or bypassed? | Corrected | - | ||
| 12.7 | On each web page, is a skip link or quick access to the main content area present (except in special cases)? | To do | T4 2026 | ||
| 12.8 | On each web page, is the tab order consistent? | Corrected | - | ||
Consultation
| RGAA criterion | Description | Processing status | Deadline | ||
|---|---|---|---|---|---|
| 13.3 | On each web page, does each office document available for download have, where necessary, an accessible version (except in special cases)? | To do | T2 2027 | ||
| 13.10 | On each web page, can features that can be used or are available by means of a complex gesture also be available by means of a simple gesture (except in special cases)? | To do | T2 2027 | ||
Non-accessible content
The following content is not accessible for the following reasons.
Non-conformities
Several non-compliance issues are described in this document, some of which recur on several pages:
- Some informative images do not have relevant alternative text.
- The contrast between the background colour and the text of some interface components is insufficient.
- Some link titles are not explicit for assistive technologies.
- Some interactive components are not implemented in an accessible manner.
- Assistive technologies do not announce that results are updated when filters are selected on certain pages.
-
Empty
tags are used to visually create space between paragraphs.
- The titles of some fields are not relevant.
- PDF documents are not accessible.
Content not subject to accessibility requirements
- BNP Paribas' Axepta payment platform
- The Flywire payment platform
Preparation of the accessibility statement
This declaration was drawn up on 20/08/2025.
Technologies used to build the website
- HTML5
- CSS
- Javascript
- PHP
Tools for assessing accessibility
- Wave
- Axe DevTools - Web Accessibility Testing
Pages of the website that have been checked for compliance
- Home - Guest
- Campaign's detail
- Login
- Forgotten password
- Registration
- Legal notice
- Data privacy policy
- Rights management
- Cookie policy
- Accessibility
- Profile area
- Home - Logged
- All campaigns
- Filling out a form
- Filling out documents
- Confirmation of file submission
- Campaigns / Programmes
- Add/edit a campaign
- Forms
- Emails
- Add/edit an email address
- Global settings
- List of files
- Consulting a file
- List of users
Feedback and contact
If you are unable to access content or a service, you can contact the website manager to be directed to an accessible alternative or obtain the content in another format.
- Send a message to accessibilite@emundus.fr
Remedy
If you notice an accessibility issue preventing you from accessing content or functionality on the website, and you report it to us but do not receive a response, you are entitled to submit your complaint or request for referral to the Defender of Rights.
There are several ways to do this:
- a contact form
- the list of delegates near you with their direct contact information
- A telephone number: 09 69 39 00 00, Monday to Friday from 8:00 a.m. to 8:00 p.m. (cost of a local call)
- a postal address in the administration directory