Stevenage Borough 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 accessibility statement applies to:
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.
The content listed below is non-accessible for the following reason(s):
(a) non-compliance with the accessibility regulations
Some text does not meet the requirements for WCAG 1.4.3 Contrast (Minimum). This is intended, as some aspects of functionality are reduced in contrast when they cannot be used. One example of this is the “Previous” button when no previous selection is available.
There are rare instances where WCAG 1.4.10 Reflow is not fully met. We believe this may be due to individual browser, monitor, or device settings, but we will continue to monitor the situation
There is intentional use of a logo that does not require Alternative Text WCAG 1.1.1 Non-text Content. The logo represents the company responsible for the build and maintenance of the website page, the name of which in conveyed in the text displayed adjacent to the image.
There is currently only one way to find other web pages which is a list of related pages. This does not conform with WCAG 2.4.5 Multiple Ways. We plan to add at least one other alternative in future, such as a site map or search.
There are 3 instances of redundant links WCAG 2.4.4 Link Purpose (In Context). These are intentional, and key to how the home page user journey functions. Links to “Current Vacancies”, “Home” and “Careers” allow the user to return to the default view of the page if filtering has been applied.
There is one instance (Upload CV) of a form control that has more than one label associated with it. WCAG 2.4.6 Headings and Labels. This issue arises because the function is linked to a plugin that generates 2 labels. We plan to review how this could be met in the future.
Standard for WCAG 3.3.3 Error Suggestion is not met. If an input error is automatically detected and suggestions for correction are known, then the suggestions should be provided to the user, unless it would jeopardise the security or purpose of the content. We plan to review how this could be met in the future.
Some elements of WCAG 4.1 guidelines regarding Robustness may not be met, such as WCAG 4.1.3 Status Messages. We plan to assess this, and address in future.
(b) the content is not within the scope of the accessibility regulations
reCAPTCHA.
Where reCAPTCHA is used, this is a free 3rd party tool which we do not have control over. reCAPTCHA does offer alternative options to visual challenges, such as an audio challenge. Both the visual and audio challenges can be navigated via keyboard control. Audio and screen reading has not been tested as part of this assessment.
This statement was prepared on 11/09/2024 by Webrecruit.
Website pages were tested using the automated testing tool wave.webaim.org by the Webrecruit Product Team, as well as manual testing using the guidelines for assessing and fixing provided by w3.org/TR/WCAG21.
The statement was last reviewed on 11/09/2024.
If you find any problems not listed on this page, or think we’re not meeting accessibility requirements, contact:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
We will consider your request and get back to you within 2 working days.
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).
