Accessibility statement

Accessibility statement for Southampton City Council

This accessibility statement applies to content published on the www.southampton.gov.uk domain as well as the following websites:

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

If you would prefer to use our onsite tools to change how you view our website please use our accessibility controls.

How accessible this website is

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

  • the search box in the website header does not change appearance when it is selected by the keyboard, so it might not be obvious when it is selected
  • some older PDF documents are not fully accessible to screen reader software
  • there are duplicate IDs on the A to Z pages, which can impact how well accessibility technology works on those pages

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’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 the digital experience team by emailing web.editor@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.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

Southampton City Council's primary website - www.southampton.gov.uk

Failures of the following success criteria occur on 20 web pages or fewer:

  • Wrap items with the same name inside a fieldset (WCAG 2.1 success criterion 1.3.1)
  • Avoid linking to anchors that do not exist (WCAG 2.1 success criterion 2.4.1)
  • Specify a title for all inline frames (WCAG 2.1 success criterion 2.4.1)
  • Ensure every page contains a heading (WCAG 2.1 success criterion 1.3.1)
  • Combine adjacent links with the same destination (WCAG 2.1 success criterion 1.1.1)
  • Avoid alternative text that is the same as adjacent text (WCAG 2.1 success criterion 1.1.1)
  • Ensure text has sufficient contrast (WCAG 2.1 success criterion 1.4.3)

Failures of the following success criteria occur on 21 web pages or greater:

Avoid using the same link text for different destinations (WCAG 2.1 success criterion 2.4.4). Our content editors are working through these to correct all instances of the same link text being used for different destinations such as other web pages. All future links will meet this criterion.

Ensure links can be used by screen readers (WCAG 2.1 success criterion 4.1.2). This only affects the image gallery on pages in our funerals section.

Fix duplicate IDs (WCAG 2.1 success criterion 4.1.1). This is an issue on our A-Z pages. All information on these pages is also found elsewhere on the website.

Ensure controls change appearance when they are selected (WCAG 2.1 success criterion 2.4.7). This issue primarily occurs when the website search box is selected but we are reviewing and correcting each instance of it.

Mark navigation as lists (WCAG 2.1 success criterion 1.3.1). This issue primarily occurs with the three social media links in the website footer, so does not present a significant barrier but all instances of this issue will be fixed.

MySouthampton - my.southampton.gov.uk

There are no more than ten failures for each of these success criteria across the website:

  • Ensure labels in the document fragment point to valid IDs (WCAG 2.1 success criterion 1.3.1)
  • Ensure form controls have labels (WCAG 2.1 success criterion 1.3.1)
  • Ensure pinch-to-zoom is enabled (WCAG 2.1 success criterion 1.4.4)
  • Identify the purpose of fields programmatically (WCAG 2.1 success criterion 1.3.5)
  • Ensure links are distinguished by more than just color (WCAG 2.1 success criterion 1.4.1)
  • Specify alternative text for all media (WCAG 2.1 success criterion 1.1.1)
  • Specify the language of every page (WCAG 2.1 success criterion 3.1.1)
  • Ensure pages don't require zooming and 2D scrolling on small screens (WCAG 2.1 success criterion 1.4.10)
  • Ensure every page contains a heading (WCAG 2.1 success criterion 1.3.1)
  • Allow users to quickly skip to content (WCAG 2.1 success criterion 2.4.1)

There are more than ten failures for each of these success criteria across the website:

  • Ensure text has sufficient contrast (WCAG 2.1 success criterion 1.4.3). This is due to the colour and size of the “Log in” text.
  • Mark navigation as lists (WCAG 2.1 success criterion 1.3.1). This occurs in the header and footer navigation.
  • Ensure controls change appearance when they are selected (WCAG 2.1 success criterion 2.4.7). This primarily relates to the left hand navigation, not the contents of the forms themselves.

This website is used for customer-facing forms spanning a range of council services. We are in the process of migrating these forms to a new platform and we are fixing the above accessibility issues throughout this process. We aim to complete the migration in early 2021.

Jobs at Southampton City Council - careers.southampton.gov.uk

The following success criteria have some instances of failure on this website:

  • Ensure text has sufficient contrast (WCAG 2.1 success criterion 1.4.3)
  • Ensure form controls have labels (WCAG 2.1 success criterion 1.3.1)
  • Ensure links can be used by screen readers (WCAG 2.1 success criterion 4.1.2)
  • Ensure headings include text (WCAG 2.1 success criterion 1.3.1)
  • Add a submit button to all forms (WCAG 2.1 success criterion 3.2.2)
  • Mark navigation as lists (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 every page contains a heading (WCAG 2.1 success criterion 1.3.1)
  • Ensure all pages have a page title (WCAG 2.1 success criterion 2.4.2)
  • Specify the language of every page (WCAG 2.1 success criterion 3.1.1)
  • Ensure pages don't require zooming and 2D scrolling on small screens (WCAG 2.1 success criterion 1.4.10)
  • Identify the purpose of fields programmatically (WCAG 2.1 success criterion 1.3.5)
  • Ensure links are distinguished by more than just color (WCAG 2.1 success criterion 1.4.1)
  • Ensure controls change appearance when they are selected (WCAG 2.1 success criterion 2.4.7)
  • Specify a title for all inline frames (WCAG 2.1 success criterion 2.4.1)
  • Specify alternative text for images inside links (WCAG 2.1 success criterion 1.1.1)

This website is entirely produced within a third-party recruitment platform. We continue to work with the supplier to resolve the above results.

Southampton Information Directory - sid.southampton.gov.uk

The following success criteria have some instances of failure on this website:

  • 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 links explain their purpose (WCAG 2.1 success criterion 2.4.4)
  • Specify a title for all inline frames (WCAG 2.1 success criterion 2.4.1)
  • Ensure all pages have a page title (WCAG 2.1 success criterion 2.4.2)
  • Ensure form controls have labels (WCAG 2.1 success criterion 1.3.1)
  • Add a scope to table headings (WCAG 2.1 success criterion 1.3.1)
  • Specify the language of every page (WCAG 2.1 success criterion 3.1.1)
  • Ensure pages don't require zooming and 2D scrolling on small screens (WCAG 2.1 success criterion 1.4.10)
  • Mark navigation as lists (WCAG 2.1 success criterion 1.3.1)
  • Ensure controls change appearance when they are selected (WCAG 2.1 success criterion 2.4.7)
  • Ensure pages don't scroll in two dimensions on small screens (WCAG 2.1 success criterion 1.4.10)
  • Ensure links are distinguished by more than just color (WCAG 2.1 success criterion 1.4.1)
  • Identify the purpose of fields programmatically (WCAG 2.1 success criterion 1.3.5)
  • Ensure text has sufficient contrast (WCAG 2.1 success criterion 1.4.3)
  • Ensure pinch-to-zoom is enabled (WCAG 2.1 success criterion 1.4.4)

We know that there are several success criterion that we need to work on for this website, which is produced within a third-party directory platform. We are currently reviewing the future of this website and how best to meet the needs of its users in every way, including accessibility. We aim to complete this review and agree a plan of action by end of March 2021.

Invest in Southampton - www.investinsouthampton.co.uk

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)
  • Ensure labels in the document fragment point to valid IDs (WCAG 2.1 success criterion 1.3.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)
  • Avoid using the same link text for different destinations (WCAG 2.1 success criterion 2.4.4)
  • Ensure links explain their purpose (WCAG 2.1 success criterion 2.4.4)
  • Combine adjacent links with the same destination (WCAG 2.1 success criterion 1.1.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 headings include text (WCAG 2.1 success criterion 1.3.1)
  • 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)
  • 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)
  • Specify the language of every page (WCAG 2.1 success criterion 3.1.1)

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:

  • Specify headings for every PDF (WCAG 2.1 success criterion 1.3.1)
  • Fix untagged PDFs (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.

PDFs and other documents

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

  • Ensure the first heading in a PDF is a H1 (WCAG 2.1 success criterion 1.3.1)
  • Ensure PDFs are machine readable (WCAG 2.1 success criterion 1.1.1)
  • 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)
  • Define a title for all PDFs (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)
  • Ensure PDF headings follow a logical order (WCAG 2.1 success criterion 1.3.1)
  • Ensure long PDFs use bookmarks to aid navigation (WCAG 2.1 success criterion 2.4.5)

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

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

Archived websites

Archived websites are outside the scope of these regulations if they’re not needed for services our organisation provides and they are not updated. Our Public Health website at www.publichealth.southampton.gov.uk meets these criteria.

Extranets

Content on extranets published before 23 September 2019 is exempt from these regulations if it has not had any major revisions since that date. Our Young Southampton website at www.youngsouthampton.org meets these criteria.

Third-party integrations and content

We require that any new third-party systems we procure for the website are compliant with the WCAG 2.1 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:

  • Idox Open Objects directory platform
  • Curtis Fitch eProcurement portal
  • Civica Spydus library management, cookie preference centre, online payments, Modern.Gov governance and meeting management
  • Cylix elearning Carer Aware training
  • Click4assistance webchat
  • ICS AI chatbot
  • Accessibility controls that change colour and font size
  • Granicus forms
  • Unit4 recruitment

Preparation of this accessibility statement

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

This website was last tested on 20 September 2020. The test was carried out internally using the Silktide automated tool as well as manual testing and review of results.

For Southampton Information Directory, we used Silktide to choose and test a random sample of 35 pages. For Invest in Southampton, we used the same method to test 100 pages. For all other websites covered by this statement, we tested all pages.

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 internally to decide on the actions we need to take. We plan to update this statement again by the end of 2020.