> For the complete documentation index, see [llms.txt](https://docs.os.uk/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/welcome/accessibility-statement-for-os-docs.md). # Accessibility Statement for OS Docs This page provides an accessibility statement for docs.os.uk, detailing compliance with Web Content Accessibility Guidelines (WCAG) 2.2 and highlighting any accessibility issues that may occur. ## Accessibility statement for docs.os.uk This accessibility statement applies to [https://docs.os.uk](https://docs.os.uk/). This website is run by Ordnance Survey. We want as many people as possible to be able to use this platform. For example, that means you should be able to: * Increase the browser font size to its largest setting without the text spilling off the screen. * Zoom in up to 200% without loss of content or functionality. * 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 recent versions of JAWS, NVDA, VoiceOver and TalkBack). [AbilityNet](https://mcmw.abilitynet.org.uk/) has advice on making your device easier to use to meet your accessibility needs. ### How accessible is docs.os.uk? We know some parts of this website are not fully accessible: * Some links, buttons and controls are not clearly labelled with adequate alt text or are not correctly exposed to assistive technology. * Some images, icons and map-based content do not have suitable text alternatives or are not marked as decorative. * Some video content does not have complete audio description available or an accessible alternative. * Some headings, lists and page relationships are not programmatically determined. * Some interactive elements on the site are not fully keyboard accessible. * Some focus indicators and meaningful graphical elements do not meet contrast requirements. * Some text and non-text content does not meet colour contrast requirements. * Some information is conveyed by position or visual presentation alone. * Some content cannot be resized or zoomed without loss of functionality. * Some status messages are not announced to screen reader users. ### Feedback and contact information 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, leave feedback on the page or get in touch using the instructions on our [Contact Us page.](https://docs.os.uk/os-downloads/resources/site-resources/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, known as the ‘accessibility regulations’. If you’re not happy with how we respond to your complaint, contact the [Equality Advisory and Support Service (EASS)](https://www.equalityadvisoryservice.com/). ### Technical information about this website’s accessibility Ordnance Survey is committed to making docs.os.uk accessible in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. ### Compliance status The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard. This website is partially compliant with the [Web Content Accessibility Guidelines version 2.2](https://www.w3.org/TR/WCAG22/) 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 #### Perceivable – information and user interface * Some images, icons and logos do not have suitable text alternatives, or decorative images are not hidden from assistive technology. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content). We plan to fix this by November 2027. * Some map images and data visualisations rely on visual presentation, colour-coded keys or image content without providing an equivalent accessible alternative. This fails WCAG 2.2 success criteria 1.1.1 (Non-text Content) and 1.4.1 (Use of Colour). We plan to fix this by November 2027. * Some video content does not have audio description or an accessible transcript that conveys the visual information in the video. This fails WCAG 2.2 success criteria 1.2.3 (Audio Description or Media Alternative) and 1.2.5 (Audio Description). We plan to fix this by November 2027. * Some information is conveyed by colour alone, particularly in map-based images and legends. This fails WCAG 2.2 success criterion 1.4.1 (Use of Colour). We plan to fix this by November 2027. * Some text and graphical elements do not meet minimum colour contrast requirements. This fails WCAG 2.2 success criteria 1.4.3 (Contrast Minimum) and 1.4.11 (Non-text Contrast). We plan to fix this by November 2027. * Some content cannot be resized or zoomed up to 200% without loss of content or functionality, including on mobile devices where zooming is restricted. This fails WCAG 2.2 success criterion 1.4.4 (Resize Text). We plan to fix this by November 2027. * Some images of text are used where real text could be used instead. This fails WCAG 2.2 success criterion 1.4.5 (Images of Text). We plan to fix this by November 2027. * Some content that appears on hover or focus cannot be dismissed, hovered over or kept visible consistently. This fails WCAG 2.2 success criterion 1.4.13 (Content on Hover or Focus). We plan to fix this by November 2027. #### Operable – user interface and navigation * There is no ‘Skip to main content’ link to let users bypass repeated navigation. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks). We plan to fix this by November 2027. * Some interactive elements, including expandable navigation controls and image zoom controls, cannot be operated using a keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). We plan to fix this by November 2027. * Some headings and labels are not descriptive enough for users to understand their purpose, particularly when navigating out of context. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels). We plan to fix this by November 2027. * Some focus indicators are missing or do not have sufficient contrast, making it difficult for keyboard users to see where they are on the page. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible) and 1.4.11 (Non-text Contrast). We plan to fix this by November 2027. * Some user-opened content, such as the cookies dialog, can obscure keyboard focus or allow focus to move behind the dialog. This fails WCAG 2.2 success criterion 2.4.11 (Focus Not Obscured). We plan to fix this by November 2027. #### Understandable – information and user interface * Some instructions rely on sensory characteristics such as position, for example referring only to content on the left-hand side of the screen. This fails WCAG 2.2 success criterion 1.3.3 (Sensory Characteristics). We plan to fix this by November 2027. * Some controls do not have labels or instructions that clearly explain their purpose or action, including copy buttons and grouped feedback controls. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions). We plan to fix this by November 2027. * Some visible labels are not included in the accessible name of the control. This may make it difficult for speech recognition users to activate controls using the visible label. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name). We plan to fix this by November 2027. #### Robust – content and reliable interpretation * Some page components use incorrect or unsupported ARIA attributes, or do not correctly expose their name, role, value or state to assistive technology. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to fix this by November 2027. * Some headings, lists, forms and page relationships are conveyed visually but are not programmatically determined. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to fix this by November 2027. * Some status messages and changes in content are not announced to screen reader users. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages). We plan to fix this by November 2027. ### Content that’s not within the scope of the accessibility regulations #### PDFs and other documents Some of our PDFs are essential to providing our services. Where possible, we plan to either fix these or replace them with accessible HTML pages. The accessibility regulations [do not require us to fix PDFs or other documents published before 23 September 2018](https://www.legislation.gov.uk/uksi/2018/952/regulation/4/made) if they’re not essential to providing our services. Any new PDFs or Word documents we publish should meet accessibility standards. ## What we’re doing to improve accessibility We are working to improve the accessibility of docs.os.uk. We are prioritising fixes for all known WCAG 2.2 A and AA issues and will update this accessibility statement as issues are fixed. ## Preparation of this accessibility statement This statement was prepared on 26 August 2026 and last reviewed on 26 August 2026. This website was last tested for compliance with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard in February 2026. The test was carried out by the Digital Accessibility Centre (DAC). The audit assessed a representative sample of docs.os.uk pages using automated checks and manual testing with assistive technologies including screen readers, voice activation software, keyboard-only navigation, screen magnification and mobile assistive technologies. ## Accessibility statements for other Ordnance Survey services Information about how we manage accessibility across our web estate, such as the OS shop, OS Data Hub and other platforms is available on the [accessibility page of the OS website](https://www.ordnancesurvey.co.uk/accessibility).