Accessibility statement for osdatahub.co.uk

This website is run by Ordnance Survey. We want as many people as possible to be able to use this website.

For example, that means you should be able to:

• Change colours, contrast levels and fonts
• Zoom in up to 300% without the text spilling off the screen
• Navigate most of the website using just a keyboard
• Navigate most of the website using speech recognition software
• Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

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

How accessible this website is

We know some parts of this website are not fully accessible:

• Some text may be difficult to read when increasing the zoom of text only
• Not all content is accessible using a keyboard only
• The tabbing order of content is not always logical
• Some content on the site does not meet the minimum recommended contrast ratio and therefore may be difficult to read

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, then please contact us.

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

Ordnance Survey is committed to making its website 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.1 AA standard, due to the non-compliances listed below.

Non-compliance with the accessibility regulations

• Images do not have appropriate alternative attributes. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-Text Content.
• Videos on the homepage do not have an accompanying text transcript. This is a failure of WCAG 2.1 success criterion 1.2.3 Audio Description or Media Alternative.
• Page regions are not correctly identified using ARIA-landmarks, with content not being included within a main landmark. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships.
• Rendering issues are present with text when zooming text only to 200%. This is a failure of WCAG 2.1 success criterion 1.4.4 Resize Text.
• Some non-textual content lacks contrast with the background page. This includes grey buttons on a white background. This is a failure of WCAG 2.1 success criterion 1.4.11 Non-Text Contrast.
• Users are unable to interact with the dropdowns present on the map download pages when navigating with NVDA. This is a failure of WCAG 2.1 success criterion 2.1.1 Keyboard.
• A ‘Skip to main content’ link is not present on the website. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks. (Fixed)
• Skipped heading levels are present on the Homepage, Pricing and Error Reporting pages. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks. (Fixed)
• The cookie notice is the last element in the focus order. This is a failure of WCAG 2.1 success criterion 2.4.3 Focus Order. (Fixed)
• The website is inaccessible to users on IE11, this may impact users who use an assistive technology that recommends its usage. This is a failure of WCAG 2.1 success criterion 4.1.1 Parsing.
• On the ‘API Dashboard’ page the ‘OS OpenData transactions’, ‘Free Premium data transactions’, and ‘Premium data transactions’ graphics are not announced by JAWS. This is a failure of WCAG 2.1 success criterion 4.1.2 Name, Role, Value.
• Error messages on the ‘Sign in’ and ‘Account’ are not announced by screen readers. In addition to this the status messages when carrying out a search are also not announced. This is a failure of WCAG 2.1 success criterion 4.1.3 Status Messages.

Departments and agencies are urgently fixing content which fails to meet the Web Content Accessibility Guidelines version 2.1 AA standard. We will update this page when issues are fixed.

Preparation of this accessibility statement

This statement was prepared on 08/10/2021. It was last reviewed on 13/07/2023.

This website was last tested on 09/12/2022. The test was carried out by Zoonou.

We used this approach on a sample of pages to test WCAG-EM.