Accessibility statement for the Modern slavery statement registry

This accessibility statement applies to the Modern slavery statement registry, at modern-slavery-statement-registry.service.gov.uk.

This website is run by the Home Office. 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 400% without the text spilling off the screen
  • 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 yet fully accessible:

  • users who are logged into the service are automatically logged out 20 minutes after the page was last refreshed – there is no warning, and no way to adjust the length of time before the session expires
  • our service includes some radio buttons that reveal content when the user selects them - users are not always notified when conditionally revealed content is expanded or collapsed (this is a known issue across GOV.UK and should be fixed by end March 2021)
  • the search filters on Find a modern slavery statement are not fully accessible
  • some tables are not fully accessible

In addition, we provide links to modern slavery statements, guidance and resources published on other websites – we do not own or manage these sites and cannot guarantee their accessibility.

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

We’ll consider your request and get back to you in 5 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 modernslaverystatements@homeoffice.gov.uk.

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).

If you are in Northern Ireland and are not happy with how we respond to your complaint you can contact the Equalities Commission for Northern Ireland who are responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’) in Northern Ireland.

Technical information about this website’s accessibility

The Home Office 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

Across the service

Logged-in users are timed out after 20 minutes of inactivity on the server – there is no warning, and no way to adjust the length of time before the session expires. This fails WCAG 2.1 success criterion 2.2.1 (timing adjustable).

Creating an account, registering organisations and managing statements

Create an account – error messages not read out when using screen readers

When creating an account, if an error occurs the page reloads and displays an error message, but the message is not read out when using a screen reader and the links which should take the user directly to where the errors are on the page do not work. The links are instead just plain text. This fails WCAG 2.1 success criterion 3.3.1 (Error Identification).

Your details/ Manage your account – ‘change’ links are not differentiated by screen readers

Screen readers do not differentiate between the different ‘change’ links on this page, and read them all aloud in the same way instead of describing the specific task (‘change password’ or ‘change email address’, for example). This fails WCAG 2.1 success criterion 2.4.4 (Link purpose) and WCAG 2.1 success criterion 4.1.1 (Parsing).

Find your organisation – ‘choose organisation’ links are not differentiated by screen readers

When users search for and select the organisations they want to register, each of the ‘Choose organisation’ links listed on the page are read out same way by screen readers. Instead, screen readers should read out the name of the organisation associated with the link so the user is certain which organisation they’re selecting. This fails WCAG 2.1 success criterion 2.4.4 (Link purpose) and WCAG 2.1 success criterion 4.1.1 (Parsing).

‘We need more information’ – unclear what the yes/no radio buttons relate to

The first time a user selects an organisation they’ve registered, the service asks the user whether this organisation was required to publish a modern slavery statement on its website in the previous year, by selecting yes or no radio buttons. When the user tabs into the radio button group the question that the radio buttons are associated with is not read out by screen readers. This fails WCAG 2.1 success criterion 3.3.2 (Labels and instructions).

Manage your modern slavery statements – table has an empty table header

After registering an organisation, users can select that organisation and manage its modern slavery statements on the service. The table on this page is not fully accessible because it is missing a table header. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships).

Adding statements to the registry – answering questions about the statement

Users add their modern slavery statements to the service by providing a URL linking to the statement on their website and answering a series of questions about the statement.

Some of the submission questions include conditionally revealed content within radio buttons or checkboxes

Users are not always notified when conditionally revealed content associated with a radio button or checkbox is expanded or collapsed - this fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

Statement URL, dates and sign off - What period does this statement cover? - no labels above date fields

Users are asked to state the dates of the period covered by the statement. The input fields do not clearly label the start date and end date - this fails WCAG 2.1 success criterion 3.3.2 (Labels and instructions). If the user enters an invalid date it is unclear which date the error message relates to, which fails WCAG 2.1 success criterion 3.3.1 (Error identification).

Modern slavery risks – Tell us about your modern slavery risks

The user is asked to describe up to 3 modern slavery risks in 3 different text boxes, and each text box has the same label. Screen reader users cannot differentiate between each of the risk fields without their own input first. This fails WCAG 2.1 success criterion 4.1.1 (Parsing).

Modern slavery risks – About this risk – country picker - ‘remove’ links are not differentiated by screen readers

Users are asked to state the countries in which their specified risks take place. The way countries are selected and the tables they’re displayed in are not fully accessible. Screen readers read out the ‘Remove’ links the same way for each country, instead of specifying the country each link relates to. This fails WCAG 2.1 success criterion 2.4.4 (Link purpose) and WCAG 2.1 success criterion 4.1.1 (Parsing).

Group statements - Which organisations are included in your group statement? – colour contrast does not meet WCAG 2.1 contrast ratio thresholds

When users specify which organisations are included in their group statement, a link displays inside a blue banner saying ‘See which organisations you’ve selected’. This link does not have enough colour contrast, which fails WCAG 2.1 success criterion 1.4.3 (Contrast).

Group statements - Review the organisations in your group statement

Users are asked to review the list of organisations they’ve said are included in their group statement. This page highlights organisations that are already included in other statements on the service. The design of this page could be improved for a screen reader so that it reads the organisation’s name before saying which other statement it’s included in. The use of blue to highlight the organisation doesn’t work as well when colour filters are applied to the page, such as yellow on black. This fails WCAG 2.1 success criterion 1.4.1 (Use of colour).

Find a modern slavery statement

Find modern slavery statements – ‘or use search filters’ link does not receive visual focus

When a user is using the filters to search for a statement, the link does not receive visual focus. On other links on the service, a link gets a yellow visual focus on click. This is missing here which doesn’t show on click or when tabbing through.This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).

Find modern slavery statements – filters for search results – missing legends

When searching for statements, users can click on the ‘or use search filters’ link to display a range of search filters (statement year, turnover or budget, and sectors). A legend should be provided when a higher-level description is necessary for groups of check boxes, radio buttons, or other form controls. These filters do not have have legends, which fails WCAG 2.1 success criterion 1.1.1 (Non-text Content) and WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

Find modern slavery statements – search results table is not coded as a table

Search results are presented visually as a table with 2 headings: ‘Modern slavery statements’ and ‘Statement year’. Both of these headings are read out initially as the user moves through the content with a screen reader - but as this content has not been coded as a table, the column headings are not read out repeatedly as the user moves down the list. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

Organisation’s modern slavery statement summary – the ‘Link to full statement’ blue box does not receive visual focus

When a user is on an organisation’s statement summary page, the ‘Link to full statement’ link text within blue box does not receive visual focus. It is read out by a screen reader and can be accessed by keyboard, but it does not receive visual focus indication. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).

Organisation’s modern slavery statement summary – tables are not coded appropriately

Tables are all done in <div> tags and do not use correct table structure such as <th> tags so that the headings are read out with each cell to maintain context. Although this is not an essential requirement in this case, as the reading order is acceptable because of the small amount of information contained within this table, it fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

Content that’s not within the scope of the accessibility regulations

At this time, we have not identified any content that is not within the scope of the accessibility regulations.

Preparation of this accessibility statement

This statement was prepared on 15 February 2021. It will be periodically reviewed during the public beta phase of the service.

This website was last tested on 2 December 2020.

Testing was carried out internally by the Home Office.

What we're doing to improve accessibility

At the time of writing this statement, our service was in private beta and had not yet gone live. We plan to address the issues listed in the ‘Non-accessible content’ section of this statement during the public beta phase, and aim to fix them by December 2021. We will also continue to monitor the accessibility of this website as it is iterated during public beta.