Accessibility statement for Learn to Code
This accessibility statement applies to the Learn to Code technical documentation at https://alphagov.github.io/learn-to-code.
This website is run by the developer community at 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 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 for the following reasons:
- some pages have redundant links
- there are issues caused by our Technical Documentation Template
Feedback and contact information
If you need any part of this service in a different format like large print, audio recording or braille, contact the GOV.UK Notify team at https://www.notifications.service.gov.uk/support.
We’ll aim to get back to you within 3 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, contact the GOV.UK Notify team at https://www.notifications.service.gov.uk/support.
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
GDS 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
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Some pages have redundant links. This is not a fail, but should be looked at under WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context).
Also, some parts of this website are not fully accessible because of issues caused by our Technical Documentation Template.
How we tested this website
We last tested this website for accessibility issues in August 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 or 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 look at the redundant links and fix the accessibility issues with the Technical Documentation Template by the end of March 2021.
We plan to look at the linked PDF documents to maximise accessibility by the end of 2020.
Preparation of this accessibility statement
This statement was prepared on 3 September 2020. It was last reviewed on 31 December 2020.
This website was last tested in August 2020. The test was carried out by the technical writing team at GDS. We used the WAVE Web Accessibility Evaluation Tool and a checklist we created with the help of the GDS accessibility team. We tested all of the website’s pages.