Accessibility statement for UK Data Service GitHub Pages

Accessibility statement for UK Data Service GitHub Pages

This accessibility statement applies to web pages authored by the UK Data Service that are hosted on GitHub Pages (in addition to its main website). GitHub Pages is a static site hosting service that publishes websites using files from a GitHub repository, referenced in About GitHub Pages. UK Data Service content hosted on GitHub Pages covered by this statement include, but are not limited to:

The UK Data Service makes the source of some of its learning and training materials available on its main GitHub repository. Some of these link to relevant GitHub web pages.

We want as many people as possible to be able to use these pages.

For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • navigate most of the website using just a keyboard
  • listen to most of the pages using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).

AbilityNet has advice on making your device easier to use if you have a disability.

GitHub Docs also provides information on how to make your experience with GitHub as accessible as possible.

How accessible the web pages are

We know some parts of this website aren’t fully accessible:

  • High levels of zoom may cause text to spill off the screen.
  • Not every feature can be used when text size is increased by 200%.
  • Language for screen readers may not be auto set.

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

If you cannot get through on the above telephone number, please leave a voicemail – we are checking our voicemail regularly.

We’ll consider your request and get back to you within seven working days.

Reporting accessibility problems with UK Data Service GitHub Pages

We have reviewed UK Data Service GitHub Pages with the aim of minimising accessibility issues. Staff who provide content for the pages are being made aware of accessibility requirements and are being trained to enable them to address these when adding new content and documents to these pages.

We’re always looking to improve the accessibility of our GitHub Pages. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, contact our Marketing and Communications Manager on 01206 872001 or contact our communications team by email.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Contacting us by phone or visiting us in person

If you contact us before your visit we can arrange liaison with local agencies to provide sign language interpreters or lip speakers through Essex University’s Disability Service, subject to cost and availability. We hope to provide audio induction loops in the future, once we have the required technology to host this service.

Find out how to contact us.

Technical information about these web pages’ accessibility

The UK Data Service is committed to making its UK Data Service GitHub Pages accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Non accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

  • At certain levels of zoom (200%) there may be a loss of functionality for some users and text may spill out of a single column format. This fails WCAG 2.2 Success criterion 1.4.10 (Reflow). We will ask our developers if they can fix this issue. If they cannot, we will contact the third-party software provider.
  • On some pages the language is not identified, or a language attribute value is invalid which can cause issues for screen readers being able to read the content in the appropriate language. This fails WCAG 2.2 success criterion 3.1.1 (language of page). We will ask our developers if they can fix this issue. If they cannot, we will contact the third-party software provider.

How we tested this website

This website was last tested on 23 February 2024. The test was carried out by UK Data Service staff, who used the WAVE accessibility tool and manual accessibility checks.

What we’re doing to improve accessibility

Our accessibility test of all the pages is ongoing and this accessibility statement will be updated when this is completed. We will also ensure we run regular accessibility checks and that any new content added meets accessibility requirements.

Preparation of this accessibility statement

This draft statement was prepared on 23 March 2024.