This accessibility statement applies to www.durhamkeyoptions.co.uk
This website is run by Durham 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:
AbilityNet has advice on making your device easier to use if you have a disability.
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 2-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: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports].
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).
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.
Durham Key Options 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 listed below.
The content listed below is non-accessible for the following reasons.
We are working with our website provider and plan to have any accessibility non-compliance resolved by the first quarter of 2021. We will update this date when we know more.
1.1.1 Non-text Content Some Text alternatives need changing as they convey the same meaning as the image.
1.3.1 Info and Relationships On the social housing application headings are not in a hierarchal order and some radio buttons are not contained within a field set or have a legend.
1.3.2 Meaningful Sequence the DOM order does not match the visual order. Users would also expect the dropdown for Property Search to be intractable straight after clicking on property search.
1.3.5 Identify Input Purpose Autocomplete not implemented on forms collecting personal information.
1.4.4 Resize text when page zoom is used to 200% the page then has two dimensional scroll and content is hidden off screen.
2.1.1 Keyboard on the Housing Options self-assessment:
Local connections as a keyboard only user and screen reader when trying to save my local connection it doesn’t do anything.
Required documents as a keyboard only user the button for “select one or more files to upload” receives no visual focus when I use my keyboard to navigate to the button.
2.1.1 Keyboard On the social housing application:
On the local connections form page as a screen reader user when trying to save local connections it doesn't do anything.
2.1.2 No Keyboard Trap On the Housing options self-assessment under 'Next steps' a popup appears after clicking 'See more' information about Private Rented and how it might be relevant to you. As a keyboard only and screen reader user there is no way to close the popup.
2.4.3 Focus Order Some pages autofocus out of sequence, for example, “Property search” in the header.
2.4.4 Link Purpose (In Context) Links on the page do not make sense when taken out of context.
2.4.5 Multiple Ways There is only one way to navigate to content. Inclusion of a Site Map would resolve this issue.
2.4.7 Focus Visible not all elements on the website that can be focused actually receive a visual indication that they are focused.
3.2.1 On Focus Some pages refresh with error messages which aren’t announced to screen reader users as they interact with the page they are unaware of the issues, for example, on the forgotten password page after entering an incorrect login reference.
3.3.1 Error Identification Enter an incorrect login reference and then click “reset,” the page refreshes with error messages. When the page refreshes your mouse is auto focused on the login reference input field with the error message appearing underneath the input field.
The screen reader user is unaware of why the form didn’t submit successfully as the error message is not read out when focused on the input field.
3.3.2 Labels or Instructions Help is positioned below or to the right of the input field, meaning the screen reader can only access this info after scrolling through forms.
3.3.3 Error Suggestion Errors are identified but the messaging does not provide a suggestion on how to enter correct information.
3.3.4 Error Prevention (Legal, Financial, and Data) it’s not possible to withdraw bid using screen reader / keyboard only. The final step is to submit without the opportunity to review, but the form is 20 pages so not practical. There is potential to add further explanatory text before submitting
4.1.1 Parsing Web page fails validation using w3 validator and there is duplicate ID use.
4.1.3 Status Messages where content is updated dynamically there should be a status message spoken by screen readers to alert to the new content. After successfully applying to reset password the page refreshes but the screen reader user is not made aware that the form has submitted correctly.
As stated in the non-compliance section, the known issues are listed below:
A program of work is now underway to address these issues and involves working with Durham County Council’s in-house developers/designers as well as third party functionality providers.
We aim to resolve the above items by September 2021.
We are currently reviewing the requirements to meet the accessibility non-compliance guidelines; we will update this section when we know more.
There's no way to skip the repeated content in the page header (for example, a skip to main content option). This doesn't meet WCAG 2.1 success criterion 2.4.1 (bypass blocks).
It's not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content. This doesn’t meet WCAG 2.1 success criterion 1.3.4 (orientation).
It's not possible for users to change text size without some of the content overlapping. This doesn't meet WCAG 2.1 success criterion 1.4.4 (resize text).
Some of our interactive forms are difficult to navigate using a keyboard for the reasons above.
We need to check our PDFs to see if they meet accessibility standards and will update this section of the accessibility statement once we have this information.
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
We are working with our website provider to improve accessibility on our website.
This statement was prepared on 11th September 2020. It was last reviewed on 11th September 2020.