Accessibility

An accessible website is one that allows people with disabilities to access its content and features without difficulty.
For example, an accessible website allows users to:

• Navigate using a screen reader and/or a braille display (commonly used by blind and visually impaired individuals).
• Customize the website’s display according to their needs (such as enlarging or shrinking text, changing colors, etc.).
• Navigate without using a mouse (using only the keyboard, a touchscreen, voice commands, or other adapted devices).

To achieve this, the website must comply with current standards during its development and updates.

MBDA is committed to making its websites and mobile applications accessible in accordance with Article 47 of French Law No. 2005-102 of February 11, 2005.

To this end, MBDA is implementing the following strategy and actions:
•   Phase 1: To improve from non-compliant to partially compliant by October 2025 (a counter-audit will be performed to this end);
•   Phase 2: To continuously improve the rate of partially compliant by January 2026.

This accessibility statement applies to the website MBDA: https://www.mbda-systems.com/.

The website https://www.mbda-systems.com/ is not compliant with version 4.1.2 of the Référentiel Général d’Amélioration de l’Accessibilité (RGAA). The non-compliances are listed below.

An accessibility audit conducted by the company Atalan on 27/03/2025 on the live website revealed that 40% of the RGAA version 4.1.2 criteria were met.

Non-compliances

List of non-compliant criteria:

• 1.1 Does each informative image have a text alternative?
• 1.2 Are decorative images properly ignored by assistive technologies?
• 1.3 For each informative image with a text alternative, is the alternative relevant (except in specific cases)?
• 1.6 Does each informative image have a detailed description when necessary?
• 1.9 When needed, is each image caption correctly associated with the corresponding image?
• 3.1 On each web page, is information not conveyed by color alone? Is this rule respected?
• 3.2 On each web page, is the contrast between text color and background color sufficiently high (except in specific cases)?
• 3.3 On each web page, are the colors used in interface components or graphical elements conveying information sufficiently contrasted (except in specific cases)?
• 4.1 Does each pre-recorded time-based media have a transcript or an audio description, if necessary (except in specific cases)?
• 4.4 For each pre-recorded synchronized time-based media with subtitles, are the subtitles relevant?
• 4.5 Does each pre-recorded time-based media have synchronized audio description, if necessary (except in specific cases)?
• 6.1 Is each link explicit (except in specific cases)?
• 6.2 On each web page, does each link have a label?
• 7.1 Are scripts compatible with assistive technologies when necessary?
• 7.5 On each web page, are status messages correctly conveyed to assistive technologies?
• 8.6 For each web page with a page title, is the title relevant?
• 8.7 On each web page, is each language change indicated in the source code (except in specific cases)?
• 8.9 On each web page, are tags not used solely for presentation purposes? Is this rule respected?
• 9.1 On each web page, is information structured using appropriate headings?
• 9.2 On each web page, is the document structure coherent (except in specific cases)?
• 9.3 On each web page, is each list properly structured?
• 9.4 On each web page, is each quotation correctly indicated?
• 10.2 On each web page, does the visible informative content remain present when stylesheets are disabled?
• 10.4 On each web page, does the text remain readable when font size is increased up to 200% (except in specific cases)?
• 10.5 On each web page, are CSS declarations for background and font colors properly used?
• 10.6 On each web page, is each link with a non-obvious nature visible in relation to the surrounding text?
• 10.7 On each web page, is the focus indicator visible for each element receiving focus?
• 10.8 On each web page, are hidden contents meant to be ignored by assistive technologies?
• 10.9 On each web page, is information not conveyed solely through shape, size, or position? Is this rule respected?
• 10.11 For each web page, can the content be presented without loss of information or functionality, and without requiring vertical scrolling for a window of 256 px height or horizontal scrolling for a window of 320 px width (except in specific cases)?
• 10.14 On each web page, can additional content revealed via CSS styles be made visible via keyboard and any pointing device?
• 11.1 Does each form field have a label?
• 11.4 In each form, is each field label properly associated and positioned next to its field (except in specific cases)?
• 11.5 In each form, are fields of the same nature grouped when necessary?
• 11.9 In each form, is each button label relevant (except in specific cases)?
• 11.10 In each form, is input validation used appropriately (except in specific cases)?
• 11.13 Can the purpose of each input field be determined to facilitate autofill with user data?
• 12.6 Are content grouping areas present on multiple web pages (headers, main navigation, main content, footer, search engine) reachable or avoidable?
• 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 when necessary (except in specific cases)?
• 13.8 On each web page, is each moving or blinking content controllable by the user?
• 13.10 On each web page, are functions available through complex gestures also available through simple gestures (except in specific cases)?

This statement was established on June 23, 2025.

Technologies Used to Build the Website

• HTML5
• CSS
• JavaScript
   

Testing Environment

Content accessibility checks were carried out using the following browser and screen reader combinations:

• Firefox 131 with NVDA 2024.3
• Firefox 131 with JAWS 2021
• Chrome 131 with Android Talkback 14.2
   

Accessibility Evaluation Tools

• Color Contrast Analyser
• HeadingsMap
• Firefox and Chrome Developer Tools
• Web Developer (extension Firefox et Chrome)
   

Website Pages Audited for Accessibility Compliance

1. Homepage
2. Contact
3. Legal
4. Search "missile"
5. Our vision and strategy
6. Product "EXOCET AM39"
7. Product "MISTRAL SIMBAD RC"
8. Innovation "Future Weapons Systems"
9. Sustainability "Act for social sustainability and benefits for people"
10. Au cœur de MBDA
11. Rejoignez-nous
12. Job Opportunities
13. Offer "Responsable technique"
14. Press releases
15. Web article "MBDA at IDEX/NAVDEX 2025 showcases innovation through cooperation with its most advanced new technologies offer"

If you are unable to access any content or service, you can contact the manager of the MBDA website to be directed to an accessible alternative or to receive the content in another format.

Send a message via our contact page.

This procedure should be used in the following situation:
You have reported an accessibility issue to the website manager that is preventing you from accessing content or services, and you have not received a satisfactory response.

• Write a message to the French Defender of Rights (Défenseur des droits).
• Contact the local representative of the Defender of Rights in your region.
• Send a letter by post (free of charge, no stamp needed):
  Défenseur des droits
  Libre réponse 71120
  75342 Paris CEDEX 07