Merge pull request #59 from alphagov/add-accessibility-statement

added accessibility statement and amended config file to show the page in the docs

config/tech-docs.yml

@@ -13,6 +13,10 @@ header_links:
   Documentation: /
   Support: https://data.gov.uk/support
 
+# Links to show in the page footer
+footer_links:
+  data.gov.uk Technical Documentation Accessibility: /accessibility-statement.html
+
 # Enables search functionality. This indexes pages only and is not recommended for single-page sites.
 enable_search: true
 

source/accessibility-statement.html.md.erb

@@ -0,0 +1,96 @@
+---
+title: Accessibility
+weight: 999
+hide_in_navigation: true
+---
+
+# Accessibility
+
+## Accessibility statement for data.gov.uk documentation
+
+This accessibility statement applies to the data.gov.uk technical documentation at [https://guidance.data.gov.uk/#data-gov-uk-technical-documentation](https://guidance.data.gov.uk/#data-gov-uk-technical-documentation).
+
+This website is run by the data.gov.uk team at the Government Digital Service (GDS). 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 problems
+- 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](https://mcmw.abilitynet.org.uk/) 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 headings do not fit with the content that follows
+- some links do not clearly explain where they lead, or that they lead to external sites
+- there is some inaccessible language
+- some tables are structured in an inaccessible way
+- there are some links to documents in PDF format that are not accessible
+
+### What to do if you cannot access parts of this website
+
+If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, [select __Report a problem__ on the data.gov.uk Support page](https://data.gov.uk/support) to message the team with details of your request.
+
+We’ll aim to reply within 2 working days.
+
+### 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, [select __Report a problem__ on the data.gov.uk Support page](https://data.gov.uk/support) to message the team with details of your request.
+
+### 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, [the Equality Advisory and Support Service (EASS)](https://www.equalityadvisoryservice.com/).
+
+## Technical information about this website’s accessibility
+
+GDS is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
+
+There are parts of this documentation that are not accessible because of [issues caused by our Technical Documentation Template](https://tdt-documentation.london.cloudapps.digital/accessibility).
+
+### Compliance status
+
+This website is partially compliant with the [Web Content Accessibility Guidelines version 2.1](https://www.w3.org/TR/WCAG21/) 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
+
+- some headings do not fit with the content that follows, for example [https://guidance.data.gov.uk/publish_and_manage_data/harvest_or_add_data/harvest_data/#dcat-data-json-fields](https://guidance.data.gov.uk/publish_and_manage_data/harvest_or_add_data/harvest_data/#dcat-data-json-fields). This fails WCAG 2.1 success criterion 2.4.6 Headings and labels
+- some links do not clearly explain where they lead, or that they lead to external sites, for example [https://guidance.data.gov.uk/publish_and_manage_data/harvest_or_add_data/harvest_data/#dcat-data-json-fields](https://guidance.data.gov.uk/publish_and_manage_data/harvest_or_add_data/harvest_data/#dcat-data-json-fields). WCAG 2.1 success criteria 2.4.4 Link purpose (in context) and 2.4.4 Link purpose (in context)
+- some tables are structured in an inaccessible way, for example [https://guidance.data.gov.uk/publish_and_manage_data/harvest_or_add_data/harvest_data/#publish-the-metadata-record](https://guidance.data.gov.uk/publish_and_manage_data/harvest_or_add_data/harvest_data/#publish-the-metadata-record). This fails WCAG 2.1 success criteria 1.3.1 Info and Relationships and 1.3.2 Meaningful Sequence
+
+There are links to PDF documents, and these PDF documents are not fully accessible, for example [https://guidance.data.gov.uk/publish_and_manage_data/harvest_or_add_data/harvest_data/#dcat-data-json-fields](https://guidance.data.gov.uk/publish_and_manage_data/harvest_or_add_data/harvest_data/#dcat-data-json-fields). This is not a fail under any WCAG 2.1 success criterion, but should be looked at to improve accessibility
+
+## How we tested this website
+
+We last tested this website for accessibility issues in September 2020.
+
+We used manual and automated tests to look for issues such as:
+
+- lack of keyboard accessibility
+- link text that’s not descriptive
+- non-unique or non-hierarchical headings
+- italics, bold and block capital formatting
+- inaccessible formatting in general
+- inaccessible language
+- inaccessible diagrams or images
+- lack of colour contrast for text, important graphics and controls
+- images not having meaningful alt text
+- problems when using assistive technologies such as screen readers and screen magnifiers
+
+## What we’re doing to improve accessibility
+
+We plan to fix the accessibility issues in the content by the end of 2020.
+
+We plan to fix the other accessibility issues by [updating our Technical Documentation Template by the end of 2020](https://tdt-documentation.london.cloudapps.digital/accessibility#using-the-technical-documentation-template-for-your-own-documentation).
+
+This statement was prepared on 15 September 2020.
+
+This website was last tested in September 2020. The test was carried out by the technical writing team at GDS. We used the [WAVE Web Accessibility Evaluation Tool](https://wave.webaim.org/) and a checklist we created with the help of the GDS accessibility team. We tested a sample page from the site.