Accessibility statement

This accessibility statement applies to revenue.scot website.

This website is run by the Revenue Scotland. We're continuously working to make revenue.scot as accessible and usable as possible for all abilities and disabilities. This includes older audiences and those with visual, hearing, cognitive or motor impairments.

We try to make our site easy to use with assistive technologies, you should be able to:

  • use your web browser to change colours, contrast levels and fonts
  • zoom in up to 300% without loss of information
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
  • access the website using a mobile or tablet.

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

The Recite Me toolbar, available at the top of each page, provides text-to-speech functionality, fully customisable styling features, reading aids and a translation tool with over 100 languages, including 65 text-to-speech voices and many other features.

How accessible this website is

We know some parts of this website aren’t fully accessible:

  • some of our pages are not fully keyboard or screen reader accessible
  • some pages have incorrect heading structure 
  • some of our links are not worded or styled properly to be accessible
  • some of our documents are not fully accessible to screen reader software
  • some images are missing a text alternative or don't provide a meaningful one 

Feedback and contact information

We’re always looking to improve the accessibility of this website.

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: info@revenue.scot with details of the problem you have encountered.

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’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

Revenue Scotland is committed to making its website 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.1 (WCAG) A and AA success criteria, with the below exceptions.

Non-accessible content

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

Non-compliance with the accessibility regulations

Visibility of content

  1. Some images don't include a meaningful text alternative so people using a screen reader are not provided with an accurate description of what the image presents. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to add a meaningful alternative text to all images over time as we review sections of this website. When we publish new content we will make sure our content meets accessibility standards.
  2. Some links don’t make sense when read on their own (for example 'here' or 'find out more'). 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). 
  3. On some elements such as the feedback form the keyboard focus is not visible. This makes it difficult for someone with a visual impairment to navigate the form and see the content properly. This fails WCAG 2.1 success criterion 2.4.7 (Focus visible).
  4. Some tables in content do not have table row headers when needed. This means assistive technologies will not read the tables correctly. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

PDFs and other documents

Some of our PDFs and other documents don't meet accessibility standards, they may be scanned PDFs or they may not be marked up correctly for assistive technologies. 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). We plan to either fix these or replace them with accessible HTML pages.

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

PDFs and office file formats

We aren't required to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

Where documents are updated and new PDF documents published, they will meet accessibility standards.

What we’re doing to improve accessibility

We haven't set up a detailed road map but here is what we actively do to improve accessibility:

  • we carefully monitor new content to make sure it meets the standards when published
  • when we make updates to our existing pages, forms and systems we also make accessibility improvements to make them compliant
  • whenever possible we publish information as web pages rather than PDF documents
  • we provide guidance to content owners and editors on creating accessible content
  • we engage with 3rd party suppliers to make sure their products that we use are accessible

Preparation of this accessibility statement

This statement was prepared on 20 May 2016. It was last reviewed on 22 January 2024.

This website was last tested on 20 February 2023 by the Digital Accessibility Team in the Scottish Government. 

The Accessibility team ran an automated test across the site, to detect compliance with WCAG 2.1 (AA). The automated tests were completed using the latest version of Axe. This was followed by a manual accessibility review of a representative sample of pages and content types and was conducted using assistive technology in accordance with the most used (JAWs and NVDA). 

We are currently implementing changes based on this test and will update this page with new information about the improvements we make.

Last updated