Updated 22 September 2020
1) Accessibility statement for Stat-Xplore
2) Feedback and contact information
3) Technical information about this website’s accessibility
4) Non-accessible content
5) What we're doing to improve accessibility
6) Preparation of this accessibility statement
This accessibility statement applies to Stat-Xplore, which is the Department for Work and Pensions’ (DWP) open data portal for statistics.
We’ve 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.
We know some parts of this website are not fully accessible:
Back to top
Stat-Xplore is browser based and holds raw statistics data. Due to this nature and scope, it is not possible to proactively state that we can provide accessible PDF, large print, easy read, audio recording or braille versions of the statistics data held on Stat-Xplore.
Data can be downloaded in the following formats:
If you need specific statistics data from this website in a different format, please contact us and we will see what we can do to help you:
We’ll consider your request and get back to you within 20 working days.
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, please contact:
Data Dissemination and Visualisation team (Data as Statistics, Digital Group) Email: Stat.Xplore@dwp.gov.uk
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).
Back to top
The Department for Work and Pensions is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to xxxxx listed below.
Back to top
The content listed below is non-accessible for the following reasons.
There may currently be a few labels that are not correctly linked to their controls. This fails WCAG 1.3 success criterion 1.3.1 (Info and Relationships). We are in the process of ensuring this is compliant by the end of September 2020.
The main table/View table has some issues, mainly to do with the spanned cells used for the row item headers. This fails WCAG 1.3 success criterion 1.3.2 (Meaningful Sequence). We previously actively hid this focus indicator like a lot of other websites. Chrome recently made a change that showed it for quite a few controls. We are in the process of ensuring it shows for all and is compliant by the end of September 2020.
We set line-spacing for some text, but it is generally single-line text and just for alignment. This fails WCAG 1.4 success criterion 1.4.12 (Text Spacing). We are in the process of ensuring this is compliant by the end of September 2020.
We use the "title" attribute for hover messages but there is one place where we use a custom tool-tip which is currently not dismissable without moving the mouse pointer. This fails WCAG 1.4 success criterion 1.4.13 (Content on Hover or Focus). We are in the process of ensuring this is compliant by the end of September 2020.
Stat-Xplore content is not operable through a keyboard interface. This fails WCAG 2.1 (Keyboard Accessible) and WCAG 2.4 success criterion 2.4.7 (Focus Visible). We are in the process of ensuring this is compliant by the end of September 2020, specifically the tree views and pop-out menus.
Pages that have a panel on the left (e.g. the schema tree for table view) might fail WCAG 2.4 success criterion 2.4.1 (Bypass Blocks). Setting the main panel (e.g. the table panel) as a "main" element may already enable jumping straight to it. We are in the process of testing and ensuring this is compliant by the end of September 2020.
Page titles might not be as detailed as required. This fails WCAG 2.4 success criterion 2.4.2 (Page Titled). Users create their own tables in Stat-Xplore, using a wide variety of variables. Page titles will therefore not be more granular than Table View, Chart View, Custom Data, but we may add the dataset name to some of the page titles if possible. We are in the process of ensuring this is compliant by the end of September 2020.
The reading order and navigation follow a logical path and are intuitive with the exception of Custom Data. This fails WCAG 2.4 success criterion 2.4.3 (Focus Order). Stat-Xplore allows users to explore the data and customise reports to suit their purposes. We are in the process of ensuring this is compliant by the end of September 2020.
Users may not be able to determine the purpose of each link from the link text alone, or from the link text and its context. This fails WCAG 2.4 success criterion 2.4.4 (Link Purpose (In Context)). We are in the process of ensuring this is compliant by the end of September 2020.
Some buttons and drop downs may not be properly identified using the appropriate tags and assistive software may not be able to determine the status of a button or any other control. This fails WCAG 4.1 success criterion 4.1.2 (Name, Role, Value). This is mostly compliant but we are in the process of ensuring this is compliant by the end of September 2020.
When status messages appear on the page, users are alerted but the message changes their focus position. This fails WCAG 4.1 success criterion 4.1.3 (Status Messages). We are in the process of ensuring this is compliant by the end of September 2020.
Back to top
WingArc, who own the SuperWEB2 software used to create Stat-Xplore, are providing DWP with scripts to upgrade Stat-Xplore and make it compliant. DWP will implement the scripts and expect that the areas of non-compliance will be fixed by the end of September 2020.
Back to top
This statement was prepared on 22 September 2020.
This website was last tested on 29 July 2020. Stat-Xplore functions were fully checked against the accessibility test report requirements.
WingArc own the SuperWEB2 software used to create Stat-Xplore. WingArc have published the SuperWEB2 Accessibility report here: https://docs.wingarc.com.au/superstar/latest/superweb2/accessibility and their own checklist with detailed notes on how SuperWEB2 complies with each item is published here: https://docs.wingarc.com.au/superstar/latest/superweb2/accessibility/wcag-2-1-checklistBack to top