View updates on coronavirus (COVID-19) and council services. A postcode checker has been launched to make it easy to find out what the COVID protection level is where you live. If you are affected and need assistance, please visit Grampian Coronavirus (COVID-19) Assistance Hub.

Technical information about this website's accessibility

Aberdeenshire 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

We listed all our content that is not accessible:

Documents

Some of our PDF and Word documents don't meet accessibility standards. For example some may be scanned PDFs or they may not be marked up so they are accessible to a screen reader. This fails WCAG 2.1 success criteria 4.1.2 (name, role value), 1.4.5 (images of text) and 1.4.9 (images of text - no exception).

PDFs and other documents published before 23rd September 2018 are exempt from meeting the accessibility regulations if they are not essential to providing our services. We make sure that any new key documents produced by us meet accessibility standards.

Forms and interactive tools

Some of our forms are built and hosted through third party software and 'skinned' to look like our website. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships). 

The language is not set in the code on some of our forms and interactive tools. This fails WCAG 2.1 success criterion 3.1.1 (language of page). 

Not all form fields, such as text areas, have a description that is explicitly associated with the field to make sure that people using assistive technologies will also know what the field is for. This fails WCAG 2.1 success criteria 1.3.1 (information and relationship),  3.3.2 (labels or instructions) and 4.1.2 (name, role, value).

When navigating with a keyboard some form elements are not highlighted on focus or the tabbing order isn't logical. This fails WCAG 2.1 success criterion 2.4.7 (focus visible).

We plan to fix accessibility issues with our forms and interactive tools as and when we make updates to them.

HTML

On some pages HTML code is used to format content rather than CSS. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships).

Images and videos

Some images don't have a text alternative or a meaningful one so people using a screen reader can't access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

Not all prerecorded videos on this website have captions. This fails WCAG 2.1 success criterion 1.2.2 (captions - prerecorded).

Live video streams don't have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live). However we don't plan to add captions to live video streams because live videos are exempt from meeting the accessibility regulations.

We work on adding meaningful alternative text to all images. We also work on adding captions to prerecorded videos or providing information in these videos in a different format, for example as text. 

Links

Some links don’t make sense when read on its own (for example 'here' or 'click here'). On some pages the same link text is used for links going to different destinations, so people might not know the difference. This fails WCAG 2.1 success criterion 2.4.4 (link purpose - in context).

Some of our link buttons have insufficient colour contrast between the link text and the background. This fails WCAG 2.1 success criterion 1.4.3 (contrast - minimum).

On some pages links within text are identified only by colour and they are missing additional visual cues such as underline. This fails WCAG 2.1 success criterion 1.4.1 (use of colour).

We work on making all links accessible. 

Language

The language is not set in the code on some of our pages. This fails WCAG 2.1 success criterion 3.1.1 (language of page). 

We plan to set language for all our pages.