Accessibility statement

This accessibility statement applies to content published on the www.southampton.gov.uk website domain.

It does not apply to content on www.southampton.gov.uk subdomains unless specified.

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

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 also options available for you to translate our webpages into other languages.

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, please call our switchboard on 023 8083 3000.

We’ll consider your request and get back to you.

Reporting accessibility problems with this website

We aim to continually 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 the digital experience team by emailing webfeedback@southampton.gov.uk or using the feedback button at the bottom of each page on the website.

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

Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment. Textphone and Minicom users can dial 18001 in front of any of our full telephone numbers to contact a council service via the British Telecom Text Relay service.

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

If you do not have access to the internet at home, you can use our website at one of our self-serve terminals in Gateway. You can also visit Gateway to speak with an advisor if you require assistance with certain enquiries and requests.

Find out how to contact us or find out more about Gateway.

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.2 AA standard, due to the non-compliances and the exemptions listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Some text links do not clearly explain their purpose, so users may not easily predict where they lead. This fails WCAG 2.2 criterion 2.4.4 (Link Purpose (In Context)).

On four cycle route pages, the controls don't show they have been selected by the keyboard so keyboard users may find it hard to open the section of the route they wish to view. This fails WCAG 2.2 criterion 2.4.7 (Focus Visible).

Navigation components are not far enough apart on some pages, so some users may find it harder to select the navigation link they wish to follow on mobile. These are almost entirely pagination links on news archive pages. This fails WCAG 2.2 criterion 2.5.8 (Target Size (Minimum)).

On four cycle route pages, the accessible names for some of the controls point to label elements that don't exist so it may be difficult for a user of assistive technologies to understand what that element does. This fails WCAG 2.2 criterion 1.3.1 (Info and Relationships).

On two pages, a small amount of text does not have sufficient contrast so some users may find it difficult to read. This fails WCAG 2.2 criterion 1.4.3 (Contrast (Minimum)).

Our homepage does not contain a top-level heading. This fails WCAG 2.2 criterion 1.3.1 (Info and Relationships).

On 24 pages which have fields the user can fill in, the user's browser may not be able to automatically complete all of the fields so they will have to be completed manually. This fails WCAG 2.2 criterion 1.3.5 (Identify Input Purpose).

On 14 pages, tables do not have headers so it might be difficult to understand what the contents of the table means. This fails WCAG 2.2 criterion 1.3.1 (Info and Relationships).

Some tables do not contain a valid scope attribute which helps users of assistive technology to understand what the header refers to This fails WCAG 2.2 criterion 1.3.1 (Info and Relationships).

In some cases, the same link text is used more than once on a webpage but does not link to the same place every time. This fails WCAG 2.2 criterion 2.4.4 (Link Purpose (In Context)).

In addition to the above instances of non-compliance on our webpages, we have a number of PDFs and other documents that are not compliant for one or more of the following reasons:

  • PDF headings do not follow a logical order. This fails WCAG 2.2 criterion 1.3.1 (Info and Relationships).
  • PDF does not use an H1 for its first heading. This fails WCAG 2.2 criterion 1.3.1 (Info and Relationships).
  • PDF does not specify a default language. This fails WCAG 2.2 criterion 3.1.1 (Language of Page).
  • Some long PDFs do not use bookmarks to aid navigation. This fails WCAG 2.2 criterion 2.4.5 (Multiple Ways).
  • PDF has a weak title or does not have a title. This fails WCAG 2.2 criterion 2.4.2 (Page Titled).
  • PDF does not have sufficient tags or headings. This fails WCAG 2.2 criterion 1.3.1 (Info and Relationships).
  • PDF is not machine readable. This fails WCAG 2.2 criterion 1.1.1 (Non-text Content).

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. Any new PDFs or other documents we publish will meet accessibility standards.

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

Older PDFs and other documents

Our website contains older PDFs that are not fully accessible. The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 unless our website users need them to use a service.

Any new PDFs or documents we publish will meet accessibility standards.

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.

Maps

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

Third-party integrations and content

We require that any new third-party systems we procure for the website are compliant with the WCAG 2.2 AA standard. Third-party systems are partly or wholly under the control of the suppliers who provide them. We are currently reviewing all third-party integrations and content on our website so we can continue to ask our suppliers to fix any accessibility issues that occur.

Third-party integrations include:

  • Proactis procurement tender portal
  • Civica Spydus library management
  • Civic UK Cookie Control consent management tool
  • HeyCentric payment system
  • Modern.Gov governance and meeting management
  • Verint forms
  • Unit4 recruitment

Preparation of this accessibility statement

This statement was prepared on 6 August 2024.

The statement was last reviewed on 6 August 2024 following testing carried out internally using the Silktide automated tool as well as manual testing and manual review of results.