We want as many people as possible to be able to use this website.
This means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible is this website
We know some parts of this website aren’t fully accessible:
- some pages are not written in plain English
- some images do not have image descriptions
- some tables do not have row headings
- screen reading software can't read parts of pages
- many documents are in PDF format and are not accessible
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website.
If you find any problems, let us know by emailing email@example.com
The Equality and Human Rights Commission (EHRC) enforces 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 you can contact the Equality Advisory and Support Service (EASS).
Technical information about this website's accessibility
Revenue Scotland is committed to making its website accessible, under 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.
Non-compliances a listed below.
Non accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
- Images on some pages do not always have suitable image descriptions. Users of assistive technologies may not have access to information conveyed in images. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content).
- Some content looks like headings but is not. This makes it difficult for screen reader users to navigate the page. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
- 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).
- Some PDF, Excel and Word publications produced since September 2018 still don't meet accessibility standards.
Content that’s not within the scope of the accessibility regulations
Many of our older PDFs and Word documents don’t meet accessibility standards. For example, they may not be structured so they’re accessible to a screen reader.
We aren't required to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs, Excel or Word documents we publish will meet accessibility standards.
How we tested this website
We use the Web Content Accessibility Guidelines V2.1 level A and level AA to test how accessible our website is.
This website was last tested on 1 April 2021.
What we're doing to improve accessibility
We are reviewing our approach and working towards meeting the regulations by:
- continuing to train our staff to create accessible services
- increasing the use of automated and manual accessibility testing in our development process
- conducting user research with people who have access needs