Skip to content

Accessibility statement for getoutside.ordnancesurvey.co.uk/

This accessibility statement applies to getoutside.ordnancesurvey.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 images do not have appropriate descriptions
  • Some form fields do not have labels
  • Some videos do not have accessible text, captions, or audio descriptions
  • Form fields have issues such as grouping
  • Colours are used incorrectly or lack sufficient contrast
  • Some text is obscured when enlarged
  • Not all content is accessible using a keyboard only
  • The tabbing order of content is not always logical
  • You are unable to skip repetitive navigation and document structure is not logical
  • Some links to the same location have different link text
  • Inconsistent focus indicators create uncertainty about your location within the document

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

Technical information about this website’s accessibility

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-accessible content

Non-compliance with the accessibility regulations

  • Accessible names are not provided or incorrectly given to linked images and informative images. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-Text Content.
  • Decorative images on the site still contain descriptive alternative attributes. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-Text Content.
  • The email form input field and checkboxes on multiple pages lack an associated text label or descriptive title. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-Text Content.
  • Embedded videos on the ‘Get outside, stay local’ page are not identified by accessible text. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-Text Content.
  • Captions are not present for pre-record video content within the ‘Get outside, stay local’ pages. This is a failure of WCAG 2.1 success criterion 1.2.2 Captions (Pre-Recorded).
  • Audio descriptions or media alternatives such as a text transcript are not present for pre-record video content within the 'Get outside, stay local’ pages. This is a failure of WCAG 2.1 success criterion 1.2.3 Audio Description or Media Alternative (Pre-Recorded).
  • Alternative audio descriptive tracks are not present for pre-recorded videos on the ‘Get outside, stay local’ page. This is a failure of WCAG 2.1 success criterion 1.2.5 Audio Description (Pre-Recorded).
  • Related groups of links such as the links within the navigation header are not grouped together using the Nav element. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships.
  • Regions of the pages are not identified with landmarks. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships.
  • Related form elements such as checkboxes are not grouped together using the fieldset/legend. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships.
  • The email form inputs across the site have not been identified with the autocomplete attribute to allow form auto filling. This is a failure of WCAG 2.1 success criterion 1.3.5 Identify Input Purpose.
  • Links within paragraphs of text are not differentiated in any other way than using colour. This is a failure of WCAG 2.1 success criterion 1.4.1 Use of Colour.
  • Text across the site, such as white text against an orange background and orange text against a white background, is present that does not have a sufficient contrast ratio against the page background. This is a failure of WCAG 2.1 success criterion 1.4.3 Contrast (Minimum).
  • Text across the renders off screen or is cut off when zooming to 200% text only zoom. This is a failure of WCAG 2.1 success criterion 1.4.4 Resize Text.
  • Zooming the page to 400% with a browser width of 1280px results in the cookie banner, placeholder text within the input field in the footer, and text within the hero container to be partially cut off. This is a failure of WCAG 2.1 success criterion 1.4.10 Reflow.
  • Page copy and links on the ‘Home’ and ‘Get outside, stay local’ pages becomes cut off or is unable to be selected when applying custom CSS text styling. This is a failure of WCAG 2.1 success criterion 1.4.12 Text Spacing.
  • Content that appears on hover is unable to be dismissed without moving the pointer cursor. This is a failure of WCAG 2.1 success criterion 1.4.13 Content on Hover or Focus.
  • Several user interface components are unable to be interacted with when using a keyboard to navigate the site. This includes dropdowns within the navigation header and the close link on the ‘Sign up’ modal. This is a failure of WCAG 2.1 success criterion 2.1.1 Keyboard.
  • The videos on the ‘Get outside, stay local’ page are not accessible when navigating with a keyboard on macOS with VoiceOver enabled. This is a failure of WCAG 2.1 success criterion 2.1.1 Keyboard.
  • Users are unable to navigate away from the cookie banner when navigating the site with a keyboard only. This is a failure of WCAG 2.1 success criterion 2.1.2 No Keyboard Trap.
  • Content that moves and updates automatically is present within the ‘Covid-19’ page, with no mechanism present to be able to pause, stop, or hide it by the user. This is a failure of WCAG 2.1 success criterion 2.2.2 Pause, Stop, Hide.
  • A correctly formed heading structure is not present to facilitate navigation across the site. This includes skipped heading levels and empty headings with no content. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks.
  • Iframes across the site lack an appropriate title. Without an appropriate title, users will not be able to determine if the content within the iframe is of importance to them. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks.
  • A ‘Skip to main content’ link or similar is currently not present on the site to allow users to bypass repeater navigational components across the pages. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks.
  • When tabbing the page with a keyboard the user is focused to content behind modals, and the focus order of the header and ‘Get outside, stay local’ page is seen to be illogical. This is a failure of WCAG 2.1 success criterion 2.4.3 Focus Order.
  • Multiple instances of identical link text are present on the ‘Home’ and ‘Get outside, stay local’ pages. This is a failure of WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context).
  • Some links do not have an accessible name. This is a failure of WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context).
  • A visible tab focus indicator is not present for the OS logo, Get outside logo, and search input field when tabbing the pages with a keyboard only. This is a failure of WCAG 2.1 success criterion 2.4.7 Focus Visible.
  • When submitting an invalid email format into the newsletter signup form, an error message is not presented to users. This is a failure of WCAG 2.1 success criterion 3.3.1 Error Identification.
  • The email input field present on all pages lacks a label with information pertaining to the required input format. This is a failure of WCAG 2.1 success criterion 3.3.2 Labels or Instructions.
  • HTML validation errors are present across the ‘Covid-19’ and ‘Get outside, stay local’ pages which may impact users of assistive technologies. This is a failure of WCAG 2.1 success criterion 4.1.1 Parsing.
  • The search function and ‘Get outside, stay local’ page do not function on Internet Explorer 11. This is a failure of WCAG 2.1 success criterion 4.1.1 Parsing.
  • When navigating all pages with either VoiceOver or TalkBack screen readers enabled, buttons within the navigation header announce as “unpronounceable”. This is a failure of WCAG 2.1 success criterion 4.1.2 Name, Role, Value.
  • ARIA menus that do not contain the required menu items are present on all pages. This may result in keyboard users being unable to interact with internal menu items. This is a failure of WCAG 2.1 success criterion 4.1.2 Name, Role, Value.
  • Error messages present when submitting forms are not announced when navigating using a screen reader. This is a failure of WCAG 2.1 success criterion 4.1.3 Status Messages.

What we’re doing to improve accessibility

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 24/09/2021. It was last reviewed on 24/09/2021.

This website was last tested on 05/08/2021. The test was carried out by Zoonou.

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