This accessibility statement applies to:
- fostering.warwickshire.gov.uk
- eliotparkconferencing.com
- skillshub.warwickshire.gov.uk
- heritage.warwickshire.gov.uk
- schools.warwickshire.gov.uk
- heartcommunityrail.org.uk
- quit4good.warwickshire.gov.uk
- dementia.warwickshire.gov.uk
- staysafecsw.info
- visit.warwickshire.gov.uk
- searchout.warwickshire.gov.uk
- wellbeing4life.co.uk
- aceadoption.com
- childfriendlywarwickshire.co.uk
- warwickshirepensionfund.org.uk
- ceremonies.warwickshire.gov.uk
- costoflivingwarwickshire.co.uk
- countryparks.warwickshire.gov.uk
- sustainablewarwickshire.co.uk
- safeinwarwickshire.com
- wrif.co.uk
- learningcatalogue.warwickshire.gov.uk
- warwickshire.livingmadeeasy.org.uk
- learninghub.warwickshire.gov.uk
- warwickshireintranet.moderngov.co.uk
- warwickshire.smartcitizen.net
- warwickshire.nsl-apply.co.uk
- library.warwickshire.gov.uk
- library3.warwickshire.gov.uk
- internal.zipporah.co.uk
- apps.warwickshire.gov.uk
- wcc.flexiroute.net
- admissions.warwickshire.gov.uk
- wcc-warwickshire-sit.powerappsportals.com
- ask.warwickshire.gov.uk
- ce0242li.webitrent.com
- planning.warwickshire.gov.uk
This website is run by Warwickshire 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:
- most older PDF documents are not fully accessible to screen reader software
- live video streams do not have captions
- some of our online forms are difficult to navigate using just a keyboard
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:
- email webmaster@warwickshire.gov.uk
- call 01926 410410 (Monday to Friday, 8am to 6.30pm)
- minicom 01926 412277 (Monday to Friday, 8am to 6.30pm)
- visit Shire Hall, Northgate Street, Warwick, CV34 4RL
We’ll consider your request and get back to you in seven days.
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 these pages or think we’re not meeting accessibility requirements, contact webmaster@warwickshire.gov.uk.
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).
This statement was prepared on 1 April 2020. It was last updated on 11 November 2022.
Technical information about this website’s accessibility
Warwickshire 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.
Compliance status
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard.
The website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Issues relating to reporting and submitting feedback
When using a keyboard to navigate the website, some controls, such as links, buttons and text fields do not change appearance to indicate they are selected. This fails WCAG AA 2.4.7. We plan to ensure that all controls change appearance when selected by May 2024 and that the controls for all future forms meet this accessibility standard.
Some interactive elements do not have an accessible name associated to them, making it difficult for screen readers to navigate the page. This fails WCAG A 1.3.1. We plan to ensure that all interactive elements have accessible names by May 2024 and that interactive elements in all future forms meet this accessibility standard.
Some forms are not able to be fully read by screen readers, which makes it difficult to navigate and complete. This fails WCAG A 1.3.1. We plan to ensure that all forms can be fully ready by screen readers by May 2024 and that all future forms meet this accessibility standard.
The colour of the text in certain parts of the website may not stand out against the background colour of the page, making it difficult to read. This fails WCAG AA 1.4.3. We plan to ensure that the colours of all the text in forms has sufficient contrast with its background by May 2024 and that the text in all future forms meets this accessibility standard.
The text on some form buttons does not stand out against the background colour, making the button text difficult to read. This fails WCAG AA 1.4.11. We plan to ensure that all form buttons have sufficient contrast with their background by May 2024 and that the buttons for all future forms meet this accessibility standard.
Not all pages have a clear title written into the code. This means a screen reader will not know which text forms the main heading of the page. This fails WCAG A 1.3.1. We plan to ensure that all pages have a suitable title written into the code by May 2024 and that all future forms meet this accessibility standard.
Some links cannot be read correctly by screen readers. This fails WCAG A 4.1.2. We plan to ensure that all links can be read correctly by screen readers by May 2024 and that the links on all future forms meet this accessibility standard.
Some parts of a page share an ID with other parts of a page, rather than being unique. This means assistive technology cannot process the content correctly. This fails WCAG A 4.1.1. We plan to ensure that all parts of form pages have unique IDs by May 2024 and that all future forms meet this accessibility standard.
The attributes of some labels are not correctly linked to the ID of the control. This fails WCAG A 1.3.1. We plan to ensure that the attributes of all labels are correctly linked to the ID of the corresponding control by May 2024 and that the labels for all future forms meet this accessibility standard.
Disproportionate burden
PDFs and other documents
Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.2 success criterion 4.1.2.
We’ve assessed the cost of fixing the issues with these documents. We believe that fixing them all now would be a disproportionate burden within the meaning of the accessibility regulations.
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 intend to have either fixed the accessibility issues with these documents or replaced them with HTML pages by September 2024.
We are carrying out a full accessibility audit of PDFs and other WCC documents linked to from the website with the aim of making as many of them as possible are accessible and that new documents comply with the WCAG 2.2 criteria.
Content that’s not within the scope of the accessibility regulations
Live video
Live video streams do not have captions. This fails WCAG 2.1 success criterion 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.
Preparation of this accessibility statement
This statement was prepared on 1 April 2020. It was last reviewed on 13 February 2024.
This website was last tested in February 2024 against the WCAG 2.1 AA standard.
All pages were tested using automated testing tools by our website team.