skip to main content skip to search skip to footer skip to accessibility statement

Accessibility statement for Southampton Data Observatory

This accessibility statement applies to data.southampton.gov.uk

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 have 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 fully accessible:

  • The 404 page requires scrolling on small screens, which makes it harder to read
  • In some cases we use the same link text for different destinations
  • Some text links don’t explain their purpose

Feedback and contact information

If you need information on this website in a different format like other languages, 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.

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

Reporting accessibility problems with this website

We are always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we are not meeting accessibility requirements, contact the Intelligence and Strategic Analysis team by emailing strategic.analysis@southampton.gov.uk or calling 023 8083 3000.

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

You can contact us on 023 8083 3000. Our address is Civic Centre, Civic Centre Road, Southampton, SO14 7LY.

Technical information about this website’s accessibility

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 less than ten instances of failure on our web pages:

  • Add headers to tables (WCAG 2.1 success criterion WCAG A 1.3.1)
  • Ensure every page contains a heading (WCAG 2.1 success criterion WCAG A 1.3.1)
  • Ensure pinch-to-zoom is enabled (WCAG 2.1 success criterion WCAG AA 1.4.4)
  • Specify alternative text for all media (WCAG 2.1 success criterion WCAG A 1.1.1)
  • Avoid alternative text that is the same as adjacent text (WCAG 2.1 success criterion WCAG A 1.1.1)
  • Add a scope to table headings (WCAG 2.1 success criterion WCAG A 1.3.1)
  • Ensure pages don't scroll in two dimensions on small screens (WCAG 2.1 success criterion WCAG AA 1.4.10)
  • Ensure form controls have labels (WCAG 2.1 success criterion WCAG A 1.3.1)
  • Identify the purpose of fields programmatically (WCAG 2.1 success criterion WCAG AA 1.3.5)
  • Add a legend for all fieldsets (WCAG 2.1 success criterion WCAG A 1.3.1)
  • Specify the language of every page (WCAG 2.1 success criterion WCAG A 3.1.1)
  • Ensure text has sufficient contrast (WCAG 2.1 success criterion WCAG AA 1.4.3)
  • Mark navigation as lists (WCAG 2.1 success criterion WCAG A 1.3.1)
  • Ensure pages don't require zooming and 2D scrolling on small screens (WCAG 2.1 success criterion WCAG AA 1.4.10)
  • Allow users to quickly skip to content (WCAG 2.1 success criterion WCAG A 2.4.1)

The following success criteria have more than ten instances of failure on our web pages:

  • Fix duplicate IDs (WCAG 2.1 success criterion WCAG A 4.1.1)
  • Ensure links explain their purpose (WCAG 2.1 success criterion WCAG A 2.4.4)
  • Ensure controls change appearance when they are selected (WCAG 2.1 success criterion WCAG AA 2.4.7)
  • Avoid using the same link text for different destinations (WCAG 2.1 success criterion WCAG A 2.4.4)

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 small 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 WCAG A 1.3.1)
  • Ensure PDFs specify a default language (WCAG 2.1 success criterion WCAG A 3.1.1)
  • Fix untagged PDFs (WCAG 2.1 success criterion WCAG A 1.3.1)
  • Specify headings for every PDF (WCAG 2.1 success criterion WCAG A 1.3.1)
  • Define a title for all PDFs (WCAG 2.1 success criterion WCAG A 2.4.2)
  • Ensure long PDFs use bookmarks to aid navigation (WCAG 2.1 success criterion WCAG AA 2.4.5)
  • Improve weak PDF titles (WCAG 2.1 success criterion WCAG A 2.4.2)
  • Ensure PDF headings follow a logical order (WCAG 2.1 success criterion WCAG A 1.3.1)

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

  • Maps

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 test all pages on the site. 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 internally to decide on the actions we need to take.

Last updated: 22 September 2020