Find out how we ensure our website can be used by people of all abilities and disabilities.

Accessibility statement

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; and
  • 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.

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.

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 to screen reader software; 
  • 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; and
  • some of our online forms are difficult to navigate using just a keyboard.

What to do if you can't access parts of this website

You can contact us if you would like information in another language or different format like accessible PDF, large print, easy read, audio recording or Braille.

We’ll consider your request and get back to you as soon as possible.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. You can email: webteam@northyorks.gov.uk if you find any accessibility problems not listed on this page or think we’re not meeting accessibility requirements. 

Enforcement procedure

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).

Contacting us by phone or visiting us in person

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.

Find out how to contact us here.

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

Content Detail
Images

Some images do not have a text alternative (or use the filename by default), so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.

Videos

Some pre-recorded videos don’t have audio captioning or a description, so the information in them isn’t available to people who cannot see or hear the video content. This fails WCAG 2.1 success criterion 1.2.2 (captions), 1.2.3 (audio description or media alternative) and 1.2.5 (audio description).

We plan to add audio captioning and descriptions for all pre-recorded videos by September 2020. 

Links

On some pages we've used the same link text that points to different URLs. This fails WCAG 2.1 success criterion 2.4.4 (link purpose in context).

We plan to correct link text on all pages by September 2020. 

Headings

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).

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).

We plan to correct our use of headings on pages by September 2020. When we publish new content we'll make sure our headings meet accessibility standards.

Language

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). 

We plan to set the defined language for all pages on the website by September 2020.

Other technical and web development issues

We plan to correct the following additional technical issues that affect some of our pages by September 2020:

Detail WCAG 2.1 success criterion
HTML is used to format content rather than CSS

1.3.1 (Information and Relationships)

Unique IDs have been duplicated to style content differently depending on the user's device

4.1.1 (Parsing)

HTML tags have repeated attributes. For example, the tag `nav` 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)
The italics tag 'i' has been used to display the social media icons in the footer 1.3.1 (Information and Relationships)
A meta refresh tag has been added to automatically redirect users to an alternative page 2.2.1 (Timing Adjustable) and 2.2.4 (Interruptions)

Content that’s not within the scope of the accessibility regulations

PDFs and other documents

Many of our 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.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. By September 2020, we plan to either fix these or replace them with accessible HTML pages or online forms.

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. 

We will work to ensure key new documents meet accessibility standards.

How we tested this website

This website was last tested on 10 September 2019 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:

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 will shortly be producing our accessibility statements for these systems.

What we’re doing to improve accessibility

We understand that maintaining an accessible website is an ongoing project and are working to resolve all identified accessibility issues which are within our control. Over the next 12 months we plan to perform a manual accessibility audit of our site. This will highlight issues that currently can’t be replicated automatically by a computer.

We will regularly monitor the accessibility of the website and ensure our content editors and web developers keep up to date with the latest accessibility best practice.

We are working with suppliers to resolve any identified accessibility issues where we do not have direct control over their product. We will also ensure that any future systems we purchase adhere to web accessibility guidelines.

We plan to provide an accessible HTML version of any new information as the primary source rather than using a PDF. 

Date of statement

This statement was published on 20 September 2019.