Accessibility for websites of the Support Centre for Data Sharing

Accessibility notice

The Support Centre for Data Sharing (SCDS) is committed to providing all of our users with equal access to our information. With accessibility at the core of our framework and design, we employ universal design principles that ensure our websites can be viewed and navigated effectively by all of our users, regardless of the device they may be using. As a webservice provided by the European Union, we adhere to the Web Accessibility Directive (Directive (EU) 2016/2102) to ensure that SCDS websites are accessible to all users including those with visual, auditory, cognitive or physical impairments, as well as those who do not possess the latest technologies. Our web content can be accessed from a variety of devices such as desktop and laptop computers, as well as web-enabled mobile devices.

How we comply

  • We adhere to the WCAG 2.1, level AA standard on the primary websites of SCDS.
  • This may differ for specific items if there are justified technical or practical reasons.
  • We publish an online accessibility statement.
  • We help users contact us to report accessibility issue.
  • We perform accessibility audits with internal and external resources.


Web Accessibility Directive (Directive (EU) 2016/2102) has not been applied to the following websites and website elements:

  • Legacy content on non-top-level pages created before January 2022: Accessibility improvements are not being applied to legacy content on pages other than the SCDS homepage and main pages (e.g. SCDS practice examples overview page), unless it was possible to apply certain accessibility features by wholesale theme or design changes. This means that pages such as individual practice examples or news pieces are not be fully accessible.
  • API Licensing Assistant, API Friendliness Checker, and API eLearning modules: These three SCDS web services are principally not designed to be web accessible.
  • Third-party content that is not funded or developed by, or under the control of, the Support Centre for Data Sharing. This applies specifically to applications and modules such as the embedding of YouTube videos on the practice example pages as well as the Twitter Embed widget (“wall”) on the SCDS homepage. As these are provided by third parties, their exact accessibility features are beyond the control of the consortium.

The 4 principles we apply when creating accessible websites:

1. Perceivable

Web content is made available to the senses: sight, hearing, and/or touch
Information and user interface components are presented to users in the most efficient way possible.

  • Screen readers: Switching off the screen and trying to navigate through the page using only the keyboard and the screen reader output gives an idea of how difficult using the website is for a user with a visual impairment.
  • Colour contrast: Vision impairments refer not only to blindness, but also to other types of visual disabilities like low visibility or colour blindness. Consequently, brightness and contrast are important considerations when designing an accessible website. A minimum contrast ratio (between foreground and background colours) of 4.5:1 is mandatory for all textual content, with the exception headings or large text where 3:1 could also be acceptable.

2. Operable

Interface forms, controls, and navigation are operable
Some users cannot use or do not have access to a mouse and rely entirely on the keyboard to interact with the web.


  • Keyboard: All functionality (including links, buttons, input fields and other interactions) must be accessible via keyboard controls
  • If certain elements are skipped while tabbing, or they do not receive focus in a logical order, the page should be corrected using proper mark-up (reviewing the underlying html structure, using CSS to control the visual presentation of the elements or adding tab-index attributes and ARIA roles when necessary).
  • Web browsers and operating systems also provide keyboard support, voice recognition (speech input) to operate websites and dictation features.

3. Understandable

Information and the operation of user interface must be understandable
The language used and website functions should be clearly understood by most users.


  • Page language: Specify the page language by using the HTML lang attribute (e.g., < html lang="en" >). In pages with multilingual content, any element using a different language than the page default must also be specified. This enables screen readers to read aloud with proper pronunciation.
  • Words: Avoid the use of ambiguous, highly technical or academic words; keep it simple whenever possible. This helps people who have difficulty understanding complex sentences, phrases, and vocabulary. In particular, it helps people with different types of cognitive disabilities.
  • Predictability: Web pages appear and operate in predictable ways. Main navigation links must always appear in the same order, interface components must behave as most users expect, even for first time visitors, etc.

4. Robust

Web content must be compatible with a wide variety of browsers and devices, including assistive technologies


  • Parsing: In content written in markup languages such as HTML or XML, elements have opening and closing tags, elements are nested according to their specifications and IDs are unique (except where specifications allow otherwise). This helps prevent errors and problems with assistive technologies.
  • Name, role, value: For all user interface components, the name and role can be programmatically determined; states, properties and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Contact us via our contact form to report accessibility issues or provide suggestions on how we can make our site more accessible. Please be as clear and detailed as possible so we may understand the nature of the problem, and provide your contact information so we may get back to you promptly.