Accessibility : Partially compliant

Accessibility : Partially compliant

Accessibility statement

Airbus undertakes to make its internet website accessible in accordance with Article 47 of Law No. 2005-102 of February 11, 2005 and Decree No. 2019-768 of July 24, 2019.

For this purpose, Airbus is working on implementing a multi-year accessibility scheme and annual action plans.

This accessibility statement applies to the website and aims to present the website's accessibility policy.


Compliance status

The website is partially compliant with the French General Accessibility Improvement Guidelines (RGAA 4.1) due to the non- compliances listed below.


Test results

The compliance audit carried out by Sopra Steria Next shows that:

  • 50% of the RGAA 4.1 criteria are respected.
  • The website has an average conformity rate of 63,9%.


This percentage corresponds to:

  • 32 compliant criteria
  • 32 non-compliant criteria
  • 42 criteria not applicable


Content not accessible

List of non-compliant criteria :

1.1Is there a text alternative for every image that conveys information?

1.2Is each decorative image properly ignored by assistive technilogies?

1.5For each image used as a CAPTCHA, is there an alternative access solution to the CAPTCHA content or function?

1.6Does each image conveying information have, where necessary, a detailed description?

3.2On each web page, is the contrast between a text colour and its background colour sufficient (except in special cases)?

6.1Is each link explicit (except in special cases)?

6.2Does every link on every web page have a title?

7.1Is each script, where necessary, compatible with assistive technologies?

7.3Can each script be controlled from the keyboard or any other pointing device (except in special cases)?

7.5On each web page, are status messages correctly rendered by assistive technologies?

8.2For each web page, is the generated source code valid according to the specified document type (except in special cases)?

8.6For each web page with a page title, is the title relevant?

8.9On each web page, tags should not be used only for presentation purposes. Is this rule followed?

9.1On each web page, is the information structured by the appropriate use of headings?

9.2Is the structure of each web page consistent (excluding special cases)?

9.3On each web page, is each list correctly structured?

10.3On each web page, does the information remain understandable when the style sheets are disabled?

10.4On each web page, does the text remain readable when the font size is increased to at least 200% (except in special cases)?

10.5In each web page, are the CSS declarations for element background and font colors used correctly?

10.6On every web page, is every link whose nature is not obvious visible in relation to the surrounding text?

10.7In each web page, for each element receiving focus, is the focus visible?

10.11For each web page, can content be presented without loss of information or functionaliy and without having to scroll vertically for a 2256 px high window or horizontally for a 320 px wide window (excluding special cases)?

10.12In every web page, can text spacing properties be redefined by the user without loss of context or functionality (except in special cases)?

11.1Does each form field have a label?

11.2Is each label associated with a form field relevant (except special cases)?

11.9In eachc form, is the title of each button relevant (excluding special cases)?

11.11In each form, is the title of each button relevant (excluding special cases)?

11.13Can the purpose of an input field be inferred to facilitate automatic filling of fields with user data?

12.1Does each set of pages have at least two different navigation systems (excluding special cases)?

12.6Can the content grouping areas present in multiple web pages (header, main navigation, main content, footer and search engine) be reached or avoided?

12.8On each web page, is the tabbing order consistent?

12.11In every web page, is additional content that appears when hovering, focusing or activating an interface component, if necessary, accessible from the keyboard?


Content not subject to the accessibility requirement:

  • Third-party content that is neither funded nor developed by the organisation concerned and which is not under its control (online framework and Youtube video player, cookie banner).


Establishment of this Accessibility Statement

This statement was made on November 10, 2023.


Technologies used for the realisation of the website

  • HTML 5
  • CSS 3
  • Javascript
  • Liferay 7.4

User agents, assistive technologies and tools used to verify accessibility

The web pages were tested with the following combinations of browsers and screen readers:

  • Voiceover + Safari on osX 13.6.1
  • Google Chrome 119 on osX 13.6.1


The following tools were used during the evaluation:

  • Developer Tools
  • Axe DevTools 4.68
  • Color Contrast Analyser


Pages of the site that have been the subject of the verification of conformity

  1. Main page
  2. Article page
  3. Search results
  4. Privacy policy
  5. Terms of use
  6. Login
  7. Login - Help
  8. Contact Us
  9. Request an access


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 form.

Contact :



If you have reported to the website manager an accessibility defect that prevents you from accessing content or one of the services of the portal and you have not received a satisfactory response, you can raise a complaint via the following steps:


  • Write a message to the Defender of Rights (
  • Contact the Defender of Rights delegate in your region (
  • Send a letter by post (free, do not put a stamp):

    Défenseur des droits

    Libre réponse 71120

    75342 Paris CEDEX 07


public navbar instanciable