Accessibility statement for My Journey Southampton

This accessibility statement applies to

This website is run by Southampton City Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • zoom in up to 300% 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

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.

There are lots of options available for you to translate pages on our website into other languages:

How accessible this website is

We know some parts of this website are not fully accessible:

  • Some links cannot be used by screen readers which makes navigation around the site more difficult
  • Some PDFs are not fully tagged
  • Some form controls do not have labels

Feedback and contact information

If you need information on this website in a different format, please contact us. We’ll consider your request and get back to you.

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, please contact us by emailing

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

Southampton City Council 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 and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

The following success criteria have some instances of failure on our web pages:

  • Ensure links are distinguished by more than just color (WCAG 2.1 success criterion 1.4.1)
  • Add a legend for all fieldsets (WCAG 2.1 success criterion 1.3.1)
  • Ensure pages don't require zooming and 2D scrolling on small screens (WCAG 2.1 success criterion 1.4.10)
  • Specify the language of every page (WCAG 2.1 success criterion 3.1.1)
  • Ensure controls change appearance when they are selected (WCAG 2.1 success criterion 2.4.7)
  • Combine adjacent links with the same destination (WCAG 2.1 success criterion 1.1.1)
  • Specify alternative text for images inside links (WCAG 2.1 success criterion 1.1.1)
  • Specify a title for all inline frames (WCAG 2.1 success criterion 2.4.1)
  • Fix duplicate IDs (WCAG 2.1 success criterion 4.1.1)
  • Ensure headings include text (WCAG 2.1 success criterion 1.3.1)
  • Ensure form controls have labels (WCAG 2.1 success criterion 1.3.1)
  • Identify the purpose of fields programmatically (WCAG 2.1 success criterion 1.3.5)
  • Ensure links can be used by screen readers (WCAG 2.1 success criterion 4.1.2)
  • Mark navigation as lists (WCAG 2.1 success criterion 1.3.1)
  • Add a scope to table headings (WCAG 2.1 success criterion 1.3.1)
  • Specify alternative text for all media (WCAG 2.1 success criterion 1.1.1)
  • Ensure pages don't scroll in two dimensions on small screens (WCAG 2.1 success criterion 1.4.10)
  • Ensure links explain their purpose (WCAG 2.1 success criterion 2.4.4)
  • Add headers to tables (WCAG 2.1 success criterion 1.3.1)
  • Avoid using the same link text for different destinations (WCAG 2.1 success criterion 2.4.4)
  • Ensure text has sufficient contrast (WCAG 2.1 success criterion 1.4.3)
  • Add a submit button to all forms (WCAG 2.1 success criterion 3.2.2)

We are working as a team to review our latest test results and take action to increase our compliance with the WCAG standards.

We have a number of PDFs and other documents that are not compliant for the following reasons:

  • Ensure PDFs specify a default language (WCAG 2.1 success criterion 3.1.1)
  • Improve weak PDF titles (WCAG 2.1 success criterion 2.4.2)
  • Fix untagged PDFs (WCAG 2.1 success criterion 1.3.1)
  • Specify headings for every PDF (WCAG 2.1 success criterion 1.3.1)
  • Define a title for all PDFs (WCAG 2.1 success criterion 2.4.2)

We are reviewing all of our PDFs to ensure that they are either replaced with an accessible web page or updated to meet these criteria. We plan to complete this by end of April 2021. Any new PDFs or other documents we publish will meet accessibility standards.

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

Pre-recorded audio and video

Our website may contain a small amount of pre-recorded audio and video published before 23 September 2020 that is not fully accessible. We are not required to make these accessible but it is our policy to do so where possible.


Our website makes use of embedded maps. We are not required to make these accessible as long as essential information is always provided in an accessible format like an address.

Preparation of this accessibility statement

This statement was prepared on 22 September 2020. It was last reviewed on 22 September 2020.

This website was last tested on 22 September 2020. The test was carried out internally using the Silktide automated tool to choose and test a random sample of 100 pages. We also manually carry out some checks as well as reviewing the automated test results.

We use Silktide’s accessibility testing to automatically test our sites every five days. We regularly review the results and manually do our own checks to decide on the actions we need to take.