Whilst West Sussex County Council strives to adhere to accepted guidelines and standards for accessibility and usability, it is not always possible to do so in all areas of the website.
The content listed below is non-accessible for the following reasons.
Non-compliance with the Accessibility Regulations
This sub-section lists issues that fail the current accessibility regulations.
During our last review of this website we have fixed all major issues that failed WCAG 2.2, please see "Resolutions Section" for detailed summary of the fixes.
Here are the issues that have come to our attention that there are areas of the website that fail to meet WCAG 2.2: -
Issues with My Account and Login Pages
Testing the login page has discovered the following accessibility issues.
- Contrast of Placeholder text is too low. This causes a failure for WCAG criteria 1.4.3 Contrast. This will be fixed by July 2025.
- Page title not descriptive enough. This causes a failure for WCAG criteria 2.4.2 Page Titled. This will be fixed by July 2025.
- Form control items are not fully labelled or have correct landmarks. This causes failures with WCAG criteria 1.3.1 Information and Relationships. This will be fixed by July 2025.
Issues with PDFs and other documents
Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be marked up to be accessible for a screen reader.
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with Easy Read Information on how users can access our services. We plan to either fix these or replace them with accessible HTML pages.
The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Issues with images, video and audio
Live video streams have captions auto added by YouTube, not all videos are currently checked for the accuracy of their captioning.
Resolutions of Non-compliance with the accessibility regulations
Since this statement was last updated the following accessibility issues have been resolved
RESOLVED: Issues with Colour Contrast being too low and items not being focus visible
The following issues were resolved from the 12th June 2025 deployment.
The Colour Contrast theme were considered too low on some content pages. These items didn't have an acceptable keyboard focus outline. This broke contrast and focus highlight regulations.
All pages now have an appropriate colour contrast theme and all link elements are focus visible.
RESOLVED: Issues with Link Text not being descriptive enough
On a previous accessibility audit it had be noted that there were different web links that didn't make sense out of context. We are constantly reviewing new items get published that they meet requirements.
RESOLVED: Issues with Mobile Devices and Screen Reflow
The following issues were resolved from the 12th June 2025 deployment.
Since the last review of this statement the hamburger menu required the user to say “Toggle Navigation” to open/close the menu. A user can now say "Menu" to expand or collapse the Hamburger Menu when viewing the website on a mobile device screen. This passes success criteria 2.5.3: Label in Name (AA) of the accessibility standards
At 400% zoom and in mobile view (320 x 256 pixels), the menu along the top of the webpage does not reflow correctly as it is no longer visible without scrolling horizontally. This failed WCAG 2.2 criteria 1.4.10 Reflow.
Content that is not within the scope of the Accessibility Regulations
This sub-section lists issues that are exempt from the current accessibility regulations. For more information see following section, ‘Exemptions to the Accessibility Regulations’.
Issues with live video
Live video streams do not have captions. This does not meet 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.
Issues with PDFs and other documents
Older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they are 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 are working to fix or replace them with accessible HTML pages. See ‘What are we doing to improve accessibility?’
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they are not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
Disproportionate burden
There are no issues that are considered a disproportionate burden.