Accessibility statement for the Hampshire County Council website
This accessibility statement applies to the public facing pages on hants.gov.uk
This website is run by Hampshire County Council. 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 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
- 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 fully accessible:
- pages with multiple search forms may cause problems for certain accessibility technologies
- autocomplete does not work on some forms as expected
- text alternatives are missing for some images, buttons and inline frames
- some scrolling or animated page elements use interactive buttons and "pips" that are missing text labels
- the faded options on our interactive service picker templates have low colour contrast with the background
- small print text used on maps is clipped when resized
- most older PDF documents are not fully accessible to screen reader software
- live video streams do not have captions
- older applications may not be fully compliant, for example grants applications
- What to do if you cannot access parts of this website
If you need information on this website in a different format, such as accessible PDF, large print, easy read, audio recording or braille:
- Complete the web accessibility form
- Add the web address (URL) of the page the content is on
- Describe the format you need, for example braille, audio CD or large print
- State which language you require
- Enter your name and email address
We will consider your request and get back to you in 5 days.This form is for web accessibility issues only. If you have other issues or questions, you can contact Hampshire County Council.
- 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 complete the web accessibility form.
- 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.
Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.
Find out how to contact us.
- Technical information about this website's accessibility
Hampshire County Council is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
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
Headings are used to organise the information on a page so a user can scan through it. They should be set up correctly so users with screen readers can also use them in this way. On some pages, headings or subheadings appear without text. This fails WCAG 2.1 1.3.1: Info and Relationships.
Most examples of this issue are caused by the page heading, which is a required part of each page's template. If the page title is left blank for any reason, the empty HTML tag will still be rendered. The web development team will look into not rendering the empty tag if the page title is left blank.
Links without a text alternative
Links represented by images or icons should also have a text alternative that describes the link's purpose to users who are blind or have low vision. Several interactive elements represented by icons are missing a text alternative. This fails WCAG 2.1 2.4.4: Link Purpose in Context, 2.4.9: Link Purpose (Link Only), and 4.1.2: Name, Role, Value.
Most examples of this issue relate to:
- sliders – tiled content arranged horizontally and controlled by "pips" to move along the row
- sliding banners – animated banner images which scroll automatically by default, but feature manual forward, backward and pause controls
Changes to these elements requires a code update to the website templates. These template changes have been raised for investigation with the web development team.
Element IDs are not unique
It is important that HTML code is formatted correctly for visitors using screen readers. No element ID should appear more than once in the HTML, as IDs should be unique to that page. Several pages have duplicate IDs at either the content level or template level. This fails WCAG 2.1 4.1.1: Parsing.
Duplicate IDs at the content level include images using the SVG format, and events sharing the same name. These examples will be fixed by the web content team as ongoing accessibility improvement work.
Two page templates and a standard newsletter form contain duplicate IDs and will need to be updated. This issue has been raised for investigation by the web development team.
Search forms use a standard set of IDs, and so any pages containing two or more search forms causes an ID conflict. Removing one or the other search is not always an option. The web development team will investigate how to provide unique IDs for each search.
Container element is empty
It is important that HTML code is formatted correctly to provide information on content structure for visitors using screen readers. Some container elements are designed to contain other elements. Some container elements are empty or missing their required elements. This fails WAI-ARIA 1.1 5.2.5: Required Owned Elements.
The majority of elements causing this issue are empty navigation, empty lists and empty table footers. This has been raised as an issue and the web development team will investigate removing empty elements when they are not required.
Colour contrast is not sufficient
Some users require high contrast between the text and background in order to read the text. Our interactive service pickers include faded header text at the top of the second or third columns until an item is selected in the preceding column. The headings are intended to be seen, but also to make it clear whether they are active or inactive. This means users with reduced vision who may not be able to see the faded examples are receiving a different user interface experience to those who can see the headings. This fails WCAG 2.1 1.4.3: Contrast (Minimum).
The web content and web development teams will look into alternative ways to present the information so it meets the needs of all users.
Image without a text alternative
All non-decorative images must have alternative text which describes the image to users who are unable to it. Some images are missing alternative text. This fails WCAG 2.1 1.1.1: Non-text Content.
All images and icons missing alternative text will be fixed by the web content team. Guidance will be issued to editors across the council to ensure alternative text is provided for all image uploads and why this is important.
Button without a text alternative
All buttons should have a text label which describes the button's function to users with assistive technology. Some forms contain "information" icon buttons that reveal more details. These buttons are missing text labels. This fails WCAG 2.1 4.1.2: Name, Role, Value.
The web team will add labels to these icon to ensure they have an accessible text alternative.
Autocomplete does not work as intended
Autocomplete allows users to fill in forms more easily by suggesting relevant personal information stored by the browser. The autocomplete must be coded correctly to ensure the correct user experience is provided. A small number of forms are using incorrect code to disable the autocomplete. This fails WCAG 2.1 1.3.5: Identify Input Purpose.
This issue has been raised to be fixed by the web development team.
Inline frame without a text alternative
Inline frames (or iframes) show content from another part of the web. All inline frames should have a text alternative that describes its function for users with assistive technology. The inline frame on the road maintenance page is missing a text alternative. This fails WCAG 2.1 4.1.2: Name, Role, Value.
This custom page template will be updated by the web development team to include a title for the inline frame.
Content that's not within the scope of the accessibility regulations
PDFs and other documents
Many of our older PDFs and Word documents do not meet accessibility standards. They may not be structured so they're accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2: Name, role value.
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. We plan to either fix these or replace them with accessible HTML pages.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they're not essential to providing our services.
Map text is clipped when resized
Users with low vision should be able to scale all text to 200% without losing any information. The small print used on our externally developed map widget does not always scale without clipping the text. This fails WCAG 2.1 1.4.4: Resize text.
Fixing this issue would require development of the external widget to meet WCAG 2.1, or replacing it with an alternative that meets the requirement. This will incur a significant cost. As the text being clipped is not the primary content intended for Hampshire County Council users, we do not see a need to replace the maps at this time. We will keep the maps under review as part of our ongoing web accessibility monitoring.
Live video streams do not have captions. This fails WCAG 2.1 1.2.4: Captions - live.
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
- How we tested this website
This statement was prepared on 24 September 2019. It was last reviewed on 21 April 2022.
This website was last tested on 11 April 2022. The test was carried out using SiteImprove and in-house quality and code reviews.
We tested the main public facing website at www.hants.gov.uk. SiteImprove crawled the website to produce the initial report. This was followed by a manual review on pages where issues were identified.