Accessibility roadmap of planned fixes
.jpg?width=1024&height=576&name=Pentagram_DarkBackground%20(002).jpg)
POUR category* |
Issue |
Resolution |
Target date |
Perceivable | Some headings are incorrectly used across the website. | We will ensure proper semantic structure is applied across the website. | August 2025 |
Operable | The purpose of some links across the site cannot be determined from the link text alone. | We will ensure links are clearly outlined in their link text. | August 2025 |
Operable | Some links are missing link text. | We will ensure all links have link text. | August 2025 |
Operable | Not all elements can be interacted with using all screen readers. Some drop-downs on the blog listing pages are not accessible. | We will amend the filters so that they can be accessed by all screen readers. | September 2025 |
Perceivable | Some images are missing alternative text. | We will manually add accurate alternative text to every image on the website. | October 2025 |
Operable | Some adjacent links go to the same URL. | We will ensure there are no redundant links across the website. | October 2025 |
Perceivable | Audio descriptions are missing from visual videos. | We will ensure all video content is accompanied by audio descriptions. | November 2025 |
Perceivable | Some content may be implemented as images of text. | We will identify all images of text and provide a suitable text alternative. | November 2025 |
Perceivable | Some graph titles are within the graphic. | We will ensure all titles have been taken out and placed within the HTML code, and future graph titles are also accessible. | November 2025 |
Perceivable | There are some cases of low contrast text across the website. | We will ensure all colour combinations are accessible for future text and will continue to update old content. | December 2025 |
*POUR - a set of four principles (Perceivable, Operable, Understandable, Robust) that guide the creation of accessible digital content, in line with the WCAG (Web Content Accessibility Guidelines).
Check out our Accessibility statement.