Accessibility

Non-compliances for highland.gov.uk

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard, due to the non-compliances and exemptions listed.

Content that is not within the scope of the accessibility regulations

Problems that fall outside 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 are not essential to providing our services.

For example, we do not plan to fix committee papers published before 23 September 2019 or reports published before 23 September 2019 as these are considered 'archives'.

Where downloads (in PDF, and other file formats) do not meet accessibility standards we plan to fix or replace them, either when they are next reviewed, or as part of our ongoing programme of review work, whichever is sooner.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Adaptable

Some of our committee meeting pages have lists which are not correctly defined as lists or contain tables without defined headers. This fails WCAG 2.0 success criterion 1.3.1. We plan to fix this by April 2026.

Some of the headings in our PDF documents are not in a logical order. This fails WCAG 2.0 success criterion 1.3.1. We plan to fix this by December 2026.

In some of our PDF documents, the first heading is not a Heading 1 (H1). This fails WCAG 2.0 success criterion 1.3.1. We plan to fix this by December 2026.

In some of our PDF documents, headings are not specified. This fails WCAG 2.0 success criterion 1.3.1. We plan to fix this by December 2026.

Some of our PDF documents are not 'tagged'. This fails WCAG 2.0 success criterion 1.3.1. We plan to fix this by December 2026.

Embedded Google maps contain tables without headers defined and form controls without labels. This fails WCAG 2.0 success criterion 1.3.1. We will review the embedded map provider currently used to see if an accessible alternative is available.

Compatible

Some of our privacy notice pages contain duplicate ID's. This fails WCAG 2.0 success criterion 4.1.1. We plan to fix this by April 2026.

Distinguishable 

When the live cameras on the Corran Ferry homepage fail to load, the error message does not have sufficient contrast. This fails WCAG 2.0 success criterion 1.4.3. We plan to raise this with the supplier of the camera feed to be resolved.

Navigable

Some of our iframes used to embed videos on a page do not specify a title. This fails WCAG 2.0 success criterion 2.4.1. We plan to fix this by April 2026.

Some of our PDFs do not have a title specified or have a weak title. This fails WCAG 2.0 success criterion 2.4.2. We plan to fix this by December 2026.

Some of our PDFs do not contain bookmarks to aid in navigation. This fails WCAG 2.0 success criterion 2.4.5. We plan to fix this by December 2026.

Readable

Some of our PDFs do not specify a default language. This fails WCAG 2.0 success criterion 3.1.1. We plan to fix this by December 2026.

Text alternatives

Some of our PDFs are not machine readable. These are mainly maps or older scanned documents. This fails WCAG 2.0 success criterion 1.1.1. Where the documents are not considered 'archives' or the maps are used for navigational purposes, we plan to fix this by December 2026.

Input modalities

Embedded Google Maps contain interactive components which are not far enough apart. This fails WCAG 2.2 success criterion 2.5.8. We will review the embedded map provider currently used to see if an accessible alternative is available.

Page last modified: 11 February 2026