This accessibility statement applies to kss.kirklees.gov.uk; an online booking management system for Kirklees Supply Service. Its main users are registered supply staff and schools.
This website is run by DotPerformance Ltd. We want as many people as possible to be able to use this website. For example, that means you should be able to:
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.
We know some parts of this website are not fully accessible:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
We’ll consider your request and get back to you in 3 working days.
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, contact us by any of the following methods:
We’ll consider your request and get back to you in 3 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).
Kirklees Supply Service 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.
The content listed below is non-accessible for the following reasons.
The tables used to show Requests and Timesheets uses a 3rd party library and accessibility testing tools flag some non-accessible warnings in our tests, however we have tested the booking process from end to end using a keyboard only and it is possible to complete the process. The 3rd party library used needs upgrading as updates are applied, making custom modifications prohibitive.
We use Google Maps to show school locations which have raised an issue with a missing alt tag. The maps are 3rd party embedded code which cannot be changed. The school address is printed on the school profile page so a screen reader would be able to read it out so the use of maps is not critical for the completion of the booking request.
The Availability Calendar uses a 3rd party library to provide calendar functionality and allow staff to view their bookings and maintain availability.
Availability can be added using the availability controls via a keyboard but it’s not possible to navigate to select an entered date to then remove the availability entry. Since its 3rd party code which needs to be periodically upgraded to keep up with latest versions, custom modifications are not feasible as they would be lost during an upgrade.
We’ve assessed the cost of fixing the issues with Non-compliance with the accessibility regulations. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in 3-years.
Schools can upload PDFs and Documents which may include forms that need to be completed prior to arriving at a placement.
The website provider does not have any control over the contents of the information provided in these documents or how accessible these documents are. It will be the responsibility of the schools to provide the information in a format that meets their own accessibility standards.
Accessibility is an important part of our development process and is considered during developing new features and testing new features for compliance with accessibility standards.
Our development process includes testing new features with Accessibility Testing Tools and Code Quality Analysis tools, so that findings from these tools are factored into the testing processes and are used as part of the sign off process.
Each code change we submit is analysed using a code analysis tool, which highlights code that is not compliant with accessibility standards. Developers are alerted of this and can make appropriate changes during the development process.
When new features are developed, we have a testing process that ensures the website works across different browsers, devices and accessibility testing and evaluation tools are used as part of the QA process prior to releasing new features.
This statement was prepared on 23rd September 2021. It was last reviewed on 29th September 2021.
This website was last tested on 29th September 2021. The test was carried out by DotPerformance Ltd.
The approach to testing was to login as Supply Staff and to complete the core booking process and profile management, both of which are the core activities users can perform.
