If you require support with any part of this website or the registration form, we will be happy to help, and you can contact us via ICT4InclusionChallenge@atos.net
Accessibility statement for ICT 4 Inclusion Challenge Website
This accessibility statement applies to all of ICT4 Inclusion Challenge Site.
This website is run by Atos. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- zoom in up to 300% without the text overflowing off the screen
- navigate all of the website using just a keyboard for navigation and operational purposes
- navigate the website using speech recognition software
- listen to the website using a screen reader (including the most recent versions of JAWS and NVDA)
We’ve also made the website text as simple as possible to understand.
How accessible this website is
We know that some parts of this website are not fully accessible:
- Multiple controls throughout the site are inaccessible via keyboard navigation.
- Parts of content within modal dialogs are not actionable.
- The heading structure is not defined correctly throughout the application.
- Visual structures are not in all cases programmatically defined.
- Sections are unlabelled despite being defined.
- Icons have not been defined with a text alternative to convey the meaning.
- The semantic structure of tables is not in all cases defined.
- Multiple controls lack labelling, both implicitly and explicitly.
- A skip to content link has not been provided.
- The focus order of content is not always in a meaningful sequence.
- A change in language is not defined where it changes to German within the site.
- Read more links, are not understandable when taken out of their onscreen context.
- States have not been conveyed for controls where required.
- Images are not marked as decorative or given an alternative text.
- When content is zoomed minor overlapping of content takes place which cause low contrast ratios between background and text.
Feedback and contact information
If you need information on this website in a different format such as accessible PDF, large print, easy read, audio recording, braille or have specific access needs, please contact:
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact:
We’ll consider your request and aim to respond to you in 10 working days.
Technical information about this website’s accessibility
Atos and GIZ are committed to making its website accessible.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to non-compliances listed below
The content listed below is non-accessible for the following reasons:
Non-compliance with the accessibility regulations
- Images have not been applied with suitable alt text or mark as decorative where required. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content). We plan to amend the text alternative of images by Q3 2022.
- The heading structure is not hierarchically structured with some sections not been appropriately defined with a heading. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to amend the heading structure by Q3 2022.
- Visual structures such as lists have not been appropriately defined programmatically. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to amend the definition of lists by Q3 2022.
- Sections within the application have not been labelled appropriately. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to amend the definition of the sections by Q3 2022.
- State information has not been defined for controls – including but not limited to popup, expanded as well as external linking. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to amend the definition of states for controls by Q3 2022.
- Tables are not provided with suitable scope attributes to define the correlation o headers. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to amend the definition of tables by by Q3 2022.
- Buttons are defined with a simple icon without a text alternative or programmatic label. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to amend the definition of the icon buttons by Q3 2022.
- When the application is resized to a minimum viewport as defined by the criterion text overlaps images making it difficult to read. This fails WCAG 2.1 success criterion 1.4.10 Reflow. We plan to make our tooltips keyboard accessible by Q3 2022.
- Content within the application cannot be access via a keyboard – including the contents of modals, specific buttons as well as share article links. This fails WCAG 2.1 success criterion 2.1.1 Keyboard. We plan to make all controls accessible via a keyboard by Q3 2022.
- The application contains a timeout that cannot be delayed, and users are not informed of. This fails WCAG 2.1 success criterion 2.2.1 Timing Adjustable. We plan to Remove/Alter/Allow users to extend the timeout by Q3 2022.
- The application has multiple navigational elements which cannot be skipped and are repeated on numerous pages. This fails WCAG 2.1 success criterion 2.4.1 Bypass Block. We plan to add a bypass block to the application by Q3 2022.
- The focus does not move to modal dialogs when opened. This fails WCAG 2.1 success criterion 2.4.3 Focus Order. We plan to alter the focus order by Q3 2022.
- The focus is not trapped within the expanded hamburger menu. This fails WCAG 2.1 success criterion 2.4.3 Focus Order. We plan to alter the focus order by by Q3 2022.
- The purpose of the home link is unclear. This fails WCAG 2.1 success criterion 3.3.2 Labels and Instructions. We plan to adjust the labelling applied by Q3 2022.
- The change in language to German from English is not defined programmatically. This fails WCAG 2.1 success criterion 3.1.2 Language of Parts. We plan to define the change in language by Q3 2022.
- Read more links lack context and are repeated multiple times with the same purpose in close proximity. This fails WCAG 2.1 success criteria 4.1.2 Name, Role, Value, 2.1.1 Keyboard, 3.3.2 Labels and instructions, 2.4.3 Focus order. We plan to adjust the definition of the read more links by Q3 2022.
- The countdown timer is not programmatically updated and announced to screen readers. This fails WCAG 2.1 success criterion 4.1.3 Status Messages. We plan to ensure that the countdown is announced by Q3 2022.
We have not identified any non-compliances that would constitute a disproportionate burden on us by fixing them. All the issues listed will be fixed in due course.
Content that’s not within the scope of the accessibility regulations
We have not identified any content that is out of scope within accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 10 August 2021 It was last reviewed on 10 August 2021.
This website was last tested on 5 August 2021. The test was carried out by Atos IT Services Accessibility and Digital Inclusion team.
The entirety of the application was tested.