Find out how we ensure our website can be used by people of all abilities and disabilities.
Contacting us by phone or visiting us in person
A text relay service for people who are D/deaf, hearing impaired or have a speech impediment is available via your telephone provider. Text relay offers text-to-speech and speech-to-text translation services. A relay assistant in a call centre acts as an intermediary, enabling people with hearing or speech impairments to communicate with other people over the telephone. You can find out more about the text relay service here. Once familiar with the service, you can use it to contact us.
Our offices have audio induction loops and we can arrange for a British Sign Language interpreter to attend any meetings you need with us. Just let the person you are meeting know and they will arrange this for you.
This accessibility statement applies to www.northyorks.gov.uk. This website is run by North Yorkshire 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.
Translating our website into other languages
Popular web browsers include the option to translate web pages by default when they detect that the website language is different to the language installed on the computer, tablet or smartphone. When browsers do not offer to automatically translate, plug-ins are often available to help you do this.
- Google Chrome should offer to translate pages automatically
- Internet Explorer can translate pages with the Google toolbar extension
- Edge can translate pages with an extension from the Microsoft store
- Safari on MacOS can translate pages with an extension available on the Safari extensions website
- Safari on iOS can translate pages with an extension from the App store
- Firefox can translate pages with various extensions
How accessible this website is
We know some parts of this website are not fully accessible. For example:
- you cannot modify the line height or spacing of text
- most older PDF documents are not fully accessible
- some of our online services are hosted by third-party suppliers and you may find navigating these services difficult depending on their level of web accessibility
- some of our online forms are difficult to navigate using just a keyboard.
Reporting accessibility problems with this website
If you find any problems that are not listed on this page or you think we’re not meeting the accessibility requirements, contact us.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
North Yorkshire 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.
This 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
We plan to correct the following content issues that affect some of our pages by September 2021.
|PDF's and other documents||
Many documents are in PDF format and are not accessible. These fail the following WCAG 2.1 success criterion:
Due to the amount of PDFs on our site we are carrying out a rolling programme of reviewing and removing them which we hope to complete by September 2021. In the meantime you can contact us to request any information they contain in an alternative format.
In some cases it may not be possible to make the PDFs fully accessible due to the complexity of the information they contain or the purpose of the PDF. In these cases we will provide accessible versions alongside them and / or contact details so the information can be requested in an alternative format.
We will ensure new documents essential for accessing our services meet accessibility standards.
We are in the process of moving our democracy system to a new provider which relies on the use of PDFs. We are working with the provider to provide an accessible solution as the project progresses.
On some pages there are empty headings, which may confuse people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (Information and Relationships) or 2.4.6 (Headings and Labels).
On some pages there are headings that have not been nested correctly, which can make content difficult to read. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (Information and Relationships).
On some pages, there is a ‘h3’ heading but no ‘h2’ heading earlier in the page. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (Information and Relationships).
On some pages the language has not been set in the code. This doesn’t meet WCAG 2.1 success criterion 3.1.1 (Language of Page).
On some pages the alternative image text is the same as the filename. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (Non-text Content) or 1.2.1 (Audio-only and Video-only)
A very small number of images have no alternative text. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (Non-text Content)
On some pages a page title has not been provided or the title is very long. This doesn’t meet WCAG 2.1 success criterion 2.4.2 (Page Titled)
On some pages, the same text has been used for links to different URLs. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (Non-text Content) or 2.4.4 (Link Purpose).
Some documents have limited using user scaling. This doesn’t meet WCAG 2.1 success criterion 1.4.4 (Resize Text).
Other technical and web development issues
We plan to correct the following additional technical issues that affect some of our pages by September 2021:
|Detail||WCAG 2.1 success criterion|
|HTML is used to format content rather than CSS||
1.3.1 (Information and Relationships), 1.4.4 (Resize Text), and 1.4.5 (Images of Text)
|HTML tags have repeated attributes. For example, the tag `div` has a repeated attribute `class`||4.1.1 (Parsing)|
|HTML tags have been closed without being opened. For example, closing an unopened tag 'p'||4.1.1 (Parsing)|
|HTML does not validate||4.1.1 (Parsing)|
|HTML does not fully conform to specification||4.1.1 (Parsing) and 4.1.2 (Name, Role, Value)|
|Fragment identifiers have been used more than once. For example, an id on a page is not unique||1.3.1 (Information and Relationships) and 4.1.1 (Parsing)|
|Some input fields do not have a descriptive label||3.3.2 (Labels or Instructions) and 2.4.6 (Headings and Labels)|
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. However we are working towards reviewing and removing as many older PDFs and documents as possible.
The accessibility regulations do not require us to make pre-recorded audio and video published before 23 September 2020 accessible. Plain text transcripts or captions will be provided alongside all videos after this date.
The accessibility regulations do not require us to make live audio and video accessible.
Third party content
Our adult social care section includes some embedded content from the Care Quality Commission to show the latest inspection reports. The link text within this does not properly specify the purpose of the link. The accessibility regulations do not require us to fix third party content that’s under someone else’s control if we did not pay for it or develop it ourselves.
The size and complexity of some of the data we are required to make public means that some tables have to be scrolled in two directions to see all of the data. This data can be made available in other formats if required.
Preparation of this accessibility statement
This statement was prepared on 21 September 2019. It was last reviewed on 23 September 2020.
This website was last tested on 22 September 2020 by Sitemorse. They provide automated testing of websites to highlight usability and accessibility issues. All pages and PDF documents within the website were tested.
We tested all content on:
- our main website platform, available at: www.northyorks.gov.uk
- 'My account' which allows customers to apply, book, report and pay for services online at: myaccount.northyorks.gov.uk. You can view the accessibility statement for My account here.
Accessibility of our other websites and online services
Some of our services that we embed or link to from our website are based on a different technical platform or provided by a third party supplier. These include (but are not limited to):
- applying for a place at a school;
- applying for a job;
- joining a library;
- enrolling on an adult learning course; and
- responding to a consultation.
We are working with our third party suppliers to ensure all our online services meet accessibility standards.
What we’re doing to improve accessibility
We plan to identify and fix issues according to the timescales shown for each area above.