Accessibility: partially compliant
Airbus Space Digital undertakes to make its website accessible in accordance with article 47 of law no. 2005-102 of 11 February 2005.
For this purpose, Airbus is working on implementing a multi-year accessibility scheme and annual action plans which will be accessible on this page.
This declaration of accessibility applies to the website: https://space-solutions.airbus.com/
Compliance status
Airbus Intelligence is partially compliant with version 4.1.2 of the Référentiel Général d’Amélioration de l’Accessibilité (RGAA) due to the non-compliances below.
Test results
An accessibility audit and counter-audit conducted by the company Atalan on 28 September 2026 on the live website revealed that 51% of the RGAA version 4.1.2 criteria were met.
Content not accessible
Non-compliance
List of non-compliant criteria:
- 1.2 Does each decoration image is correctly ignored by assistive technologies?
- 1.4 For each image used as a CAPTCHA or as a test image, with a text alternative, does this alternative describe the nature and the purpose of the
image? - 1.5 For each image used as a CAPTCHA, is a solution for alternative access to the content or to the purpose of the CAPTCHA available?
- 1.6 Does each image conveying information have a detailed description if necessary?
- 3.2 On each web page, is the contrast between the text and background colors sufficient (except in particular cases)?
- 3.3 On each web page, are the colours used in the interface components or graphic elements containing information sufficiently contrasted (except in particular cases)?
- 4.1 Does each prerecorded time-based media have a text transcript or an audio description if necessary?
- 4.3 Does each prerecorded synchronised time-based media have closed captions if necessary?
- 4.5 Does each prerecorded time-based media have a synchronised audio description if necessary?
- 5.3 For each layout table, is the linearised content still understandable?
- 5.6 For each data table, are each column header and each row header correctly identified?
- 5.7 For each data table, is each cell associated with its header cell using the appropriate technique (except in particular cases)?
- 6.1 Is each link explicit?
- 6.2 On each web page, does each link, have a title?
- 7.1 Does each script support assistive technologies, if necessary?
- 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?
- 9.1 On each web page, is information structured by the appropriate use of headings?
- 9.2 On each web page, is the document outline coherent?
- 9.3 On each web page, is each list structured appropriately?
- 10.2 On each web page, is visible content carrying information still available when style sheets or images are disabled?
- 10.3 On each web page, is information still understandable when style sheets are disabled?
- 10.7 On each web page, is the focus visible for each element that receives focus?
- 10.9 On each web page, information must not be conveyed by shape, size or location alone. Has this rule been followed?
- 10.12 On each web page, can the text spacing properties be redefined by the user without loss of content or functionality (except in particular cases)?
- 10.14 In each web page, can additional contents appearing via CSS styles only be made visible on the keyboard and by any pointing device?
- 11.1 Does each form field have a label?
- 11.5 In each form, are fields of same nature grouped together, if necessary?
- 11.10 In each form, is the input control used in a relevant way?
- 12.6 Can the content grouping areas present in several web pages (header, main navigation, main content, footer and search engine areas) be reached or avoided?
- 12.8 On each web page, is tabbing order consistent?
- 13.3 On each web page, does each office document that can be downloaded have an accessible version if necessary (except in special cases)?
- 13.8 On each web page, can each moving or blinking content be controlled by the user?
- 13.10 On each web page, can the functionalities that can be used or available by means of a complex gesture also be available by means of a simple gesture (except in particular cases)?
- 13.11 On each web page, can actions triggered by a pointing device on a single point on the screen be cancelled (except in particular cases)?
Establishment of this accessibility statement
This statement was established on 28 September 2026.
Technologies used for the realisation of the website
- HTML5
- CSS
- JavaScript
Test environment
The web page tests were carried out with the following combinations of web browsers and screen readers:
- Firefox 131 with NVDA 2024.3
- Firefox 131 with JAWS 2021
- Chrome 131 with Android Talkback 14.2
The following tools were used during the evaluation
- WCAG contrast checker
- HeadingsMap
- Web developer
- ARC Toolkit
- PAC (PDF Accessibility Checker)
Site pages checked for compliance
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: spacesolutions.accessibility@airbus.com
Remedies
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 (https://formulaire.defenseurdesdroits.fr/)
- Contact the Defender of Rights delegate in your region (https://www.defenseurdesdroits.fr/saisir/delegues)
- Send a letter by post (free, no to add a stamp):
Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07