Farm Biodiversity Scotland web application - Accessibility statement

https://www.nature.scot/doc/farm-biodiversity-scotland-web-application-accessibility-statement

This accessibility statement applies to the Farm Biodiversity Scotland web application.

How accessible this website is

We know some parts of the website are not fully accessible. For example:

  • some images do not have alternative text.
  • some images are annotated with a font colour that does not have sufficient contrast against the background.
  • in some limited cases, there is insufficient colour contrast between text and its background
  • in some limited cases, there is no visual indication of where the focus is for keyboard navigation
  • in some limited cases, certain elements are not reachable by keyboard.

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, or if you need information on this website in a different format like an accessible PDF, contact: [email protected].

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you contact us with a complaint and you’re not happy with our response, contact the Equality Advisory and Support Service (EASS). 

Technical information about this website’s accessibility

NatureScot is committed to making this web application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances, listed below.

Non-accessible content

The content that is not accessible is outlined below with details of:

  • where it fails the success criteria
  • planned dates for when issues will be fixed.

Non-compliance with the accessibility WCAG 2.2 regulations

Some images do not have a text alternative, so people using a screen reader cannot access the information. 

This fails WCAG 2.2 success criterion 1.1.1 (Non-text content).

We plan to add text alternatives for all images by 31st December 2025. When we publish new content in the meantime, we will make sure the images meet accessibility standards.

Some images are annotated with a font colour that does not have sufficient contrast against the background. This fails WCAG 2.2 success criterion 1.4.3. (Contrast (Minimum)).

We plan to modify these images to ensure that the annotation has sufficient contrast in all cases by 31st December 2025. When we publish new content in the meantime, we will make sure our use of annotated images meets accessibility standards.

In a limited number of places, at log in and when carrying out habitat condition assessments, the colour contrast between the green background colour and white text in a button is not sufficient. This fails WCAG 2.2 success criterion 1.4.3. (Contrast (Minimum)). 

At this stage, we have chosen not to make changes to the use of the colour #43D571 with bold white text as its use has been carefully considered and documented as an intentional design decision and maintains visual brand consistency. The button is the only call to action button on the screen and is surrounded by ample white space, ensuring visual prominence and user focus. We will continue to review this and may incorporate more inclusive design principles in future iterations. However, based on current resource constraints and user feedback, we are prioritising improvements with higher overall impact.

In a limited number of places, specifically in the Helpdesk function, which is provided by an external application, the colour contrast between the green background colour and white text in a button is not sufficient. This fails WCAG 2.2 success criterion 1.4.3. (Contrast (Minimum)). We plan to rectify this by 31st December 2025. 

The Helpdesk button, and some buttons within this function, are not  reachable by keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). We plan to ensure that all elements are reachable and operable by keyboard by 31st December 2025. When we implement new functionality in the meantime, we’ll make sure it is reachable by keyboard.

The Helpdesk/ Get in touch button does not currently have a visible focus indicator, so it may be difficult for users using keyboard only navigation to operate this function. 

This fails WCAG 2.2 success criterion 2.4.7 (Focus visible).

We plan to ensure each item receiving focus has a visible indicator by 31 December 2025. 

Disproportionate burden

We are not claiming that any of our accessibility issues are disproportionate to fix.

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

All of the accessibility issues are within the scope of the accessibility regulations. 

Preparation of this accessibility statement

This website was last tested on 01 March 2025 against the WCAG 2.2 AA standard. The test was carried out by the NatureScot Accessibility Officer. All public-facing pages were tested using manual methods and automated testing tools to the WCAG 2.2 AA standard. This statement was prepared on 30 September 2025. It was last reviewed on 30 September 2025.