Non-compliance with the accessibility regulations
Illogical heading structure
Some pages across the site do not follow a logical order with missing heading levels. Screen reader users use the heading structure to navigate and understand the page content. With an illogical heading structure, they will find this more difficult. This issue falls under the, 1.3.1 (A), 2.4.6 (AA) WCAG 2.1 violation(s).
Tables with incorrect markup
Some tables lack row headers. Screen reader users can find this hard to navigate. This issue falls under the, 1.3.1 (A) WCAG 2.1 violation(s).
Live feed videos missing text alternatives and/or audio description
Transcripts are provided for most videos on the website. However, there are no transcripts or audio descriptions for live press-conference feeds. We try to provide audio descriptions for videos if requested. This issue falls under the 1.2.1 (A), 1.2.2 (A) WCAG 2.1 violation(s).
Feedback form CAPTCHA
The feedback form on each website page includes a CAPTCHA (reCAPTCHA) that is required to complete the form. This is provided by a third party. Although the CAPTCHA uses a checkbox, this is replaced by an image challenge under certain conditions. Users with visual impairments who are unable to complete the CAPTCHA cannot successfully submit the form. This issue falls under the 1.1.1 (A) WCAG 2.1 violation and cannot be fixed by us.
Images – text alternative redundant, too long or missing
Some complex images lack alternative text. These include complex charts and graphs. Screen-reader users will not be able to understand the content, but the underlying data is provided wherever possible.
In other instances, screen reader users may find the alternative text long or redundant, making it time consuming to read and understand.
There are also embedded third-party Flourish charts that lack alternative text and an alternative format to assistive technology. This issue will be fixed by Flourish by December 2021.
This issue falls under the 1.1.1 (A), 1.4.5 (AA) WCAG 2.1 violation(s).
Adjacent image and text links for the same resource
Several text links and images go to the same resource. This can be confusing and frustrating for screen reader users having to access each link for the same resource. This issue falls under the 1.1.1 (A), 2.4.4 (A) WCAG 2.1 violation(s).
Colour alone used to convey information
Colour alone is used to convey information on charts and graphs. Non-sighted users and users with certain visual impairments will not be able to perceive the information. The underlying data is provided wherever possible. This issue falls under the 1.3.1 (A), 1.4.1 (A) WCAG 2.1 violation(s).
Inaccessible embedded interactive presentation elements
There is embedded third-party Tableau content that consists of numerous focusable elements. These are not reachable and operable via the keyboard. Keyboard and screen-reader users will not be able to use them. This issue falls under many WCAG 2.1 violation(s) and cannot be fixed by us.
Low colour contrast on the search bar
The error message on the search bar on the homepage does not have enough contrast between the foreground text and background colours. Text with low colour contrast makes it more difficult to read for users with visual impairments. This issue falls under the 1.4.3 (AA) WCAG 2.1 violation(s).
Error messages do not help users correct their errors
We use third-party providers for the feedback form on all pages and the subscribe to emails form. When a user makes a mistake submitting either form, error messages are provided. However, some of them lack information to help users correct their errors. This issue falls under the 3.3.3 (AA) WCAG 2.1 violation(s) and cannot be fixed by us.
Footnotes inaccessible to assistive technology
In several historical pages with charts, the relationship between the text/symbol and the footnote is not perceivable to assistive technology. This falls under the 1.3.1 (A), 4.1.2 (A) WCAG 2.1 violation(s).
Maths equations not correctly conveyed to assistive technology
In some instances, maths equations lack the correct mark-up so their meaning is not correctly conveyed to assistive technology. Screen-reader users may therefore have difficulty understanding the equations. This issue falls under the 1.3.1 (A) WCAG 2.1 violation(s).
Links to non-HTML documents missing file type and file size information
Across the website, some links lack the file-type or file-size information. This issue falls under the 2.4.4 (A).
PDFs and non-HTML documents
Many documents may not be suitable for users of assistive technology in a number of ways including missing text alternatives and missing document structure. This issue falls under the 1.1.1 (A), 1.4.5 (A), 1.3.1 (A), 2.4.6 (AA) WCAG 2.1 violation(s).
We provide a HTML version of our most popular publications and we are striving to make any new PDFs and Word documents we publish meet accessibility standards, but this may not always be possible. If you require an accessible version of any of the documents on our website, please let us know by emailing us at email@example.com.