Accessibility statement

This website is run by Joint Nature Conservation Committee (JNCC) on behalf of Scottish Government.

We want remotesensingdata.gov.scot to be accessible and usable for as many people as possible.

How accessible this website is

We know some parts of this website are not fully accessible:

• On the map page, the dataset and file pickers for downloading data and navigating to other content are not available to or usable with screen readers. The elements are not keyboard operable.
• You cannot modify the line height or spacing of text.
• You cannot skip to the main content when using a screen reader.

Feedback

If you cannot access any part of this site or want to report an accessibility problem, please tell us.

AbilityNet has advice on making your device easier to use if you have a disability.

Enforcement procedure

The Equality and Human Rights Commission enforces the accessibility regulations (the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018).

If you're not happy with how we respond to your feedback, contact the Equality Advisory and Support Service. They are an independent advice service. They will advise you on what to do next.

Compliance statement

Scottish Government is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. This accessibility statement applies to remotesensingdata.gov.scot. It was prepared on 7 February 2020.

An accessibility expert provided informal advice for this website in December 2019. Many of the issues found were fixed. 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

Non compliance with the accessibility regulations

We plan to fix the following by June 2020:

• Some images do not have a text alternative (WCAG 2.1 success criterion 1.1.1 non-text content).
• Some buttons do not have a description (WCAG 2.1 success criterion 1.3.1 info and relationships).
• The tab structure for the pages are not obviously links (WCAG 2.1 success criterion 1.3.3 sensory characteristics).
• Most of the links are identified using color alone (WCAG 2.1 success criterion 1.4.1 use of color).
• Some text does not have enough contrast with the background color (WCAG 2.1 success criterion 1.4.3 contrast: minimum).
• Some buttons do not have enough contrast with the background color (WCAG 2.1 success criterion 1.4.11 non-text contrast).
• The hover-over tooltips do not persist when the pointer is over the tooltip text (WCAG 2.1 success criterion 1.4.13 content on hover or focus).
• It is not possible to skip the main menu in each page to get straight to the page content (WCAG 2.1 success criterion 2.4.1 bypass blocks).
• Some of the link text is not as clear as it could be for a screen reader (WCAG 2.1 success criterion 2.4.4 link purpose (in context).
• Some buttons do not have the same programmatic name as that which is visible on the screen (WCAG 2.1 success criterion 2.5.3 label in name).
• Some buttons are not named correctly so that the additional information they provide is hidden to some people (WCAG 2.1 success criterion 4.1.2 name, role, value).
• The status messages are not clear for those using alternative technologies (WCAG 2.1 success criterion 4.1.3 status messages).

We plan to fix the following by April 2021:

• Choosing and downloading the data is not possible using a keyboard alone (WCAG 2.1 success criterion 2.1.1 keyboard).
• On some internet browsers the focus indicator when using the keyboard to tab through the content is not very visible (WCAG 2.1 success criterion 2.4.7 focus visible).

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

• We have noticed that the bounding box used to filter to a desired dataset on the map page is only operable using a mouse (WCAG 2.1 success criterion 2.5.1 pointer gestures). This is under review.