Accessibility


This website is run by Registers of Scotland. 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)

We’ve also made the website text as simple as possible to understand.

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:

  • headings are not always in the correct order
  • some page titles don't describe the page
  • colour contrast isn't good enough in some areas
  • tables are difficult to understand with screen reading software
  • screen reading software can't read parts of pages
  • screen reading software isn't informed when change happens on a page
  • most older PDF documents aren't fully accessible to screen reader software

What to do if you can't access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

We’ll consider your request and get back to you in two days where we will be able to advise you further.

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 website.feedback@ros.gov.uk or call us on 0800 169 939.

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 you can contact the Equality Advisory and Support Service (EASS).

Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

We can also arrange an interpreter for foreign languages if you inform us to prior to your visit or if you need a call back.

Our responses can be provided in accessible PDF, large print, easy read, audio recording or braille.

Find out how to contact us

Technical information about this website's accessibility

Registers of Scotland is committed to making its website accessible, in accordance with 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, due to the non-compliances below.

Non accessible content

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

Non compliance with the accessibility regulations

Some pages don’t have headings in the correct order.

This means they can’t be navigated in the correct order when using a screen reader. Also, some of the titles and headings don’t correctly reflect the content of the page.

This doesn’t meet WCAG 2.1 success criterion 2.4.6 (headings and labels).

Some elements of the page aren’t readable by screen readers.

For example:

  • page titles
  • structures
  • link text
  • model dialog boxes
  • action buttons

This doesn’t meet WCAG 2.1 success criterion 2.4 (navigable) or success criterion 2.4.4 (link purpose in context).

The colour contrast fails to meet the minimum requirement in areas, so elements of the page could be difficult to see. This doesn’t meet WCAG 2.1 success criterion 1.4.3 (contrast) and success criterion 1.2.11 (non-text contrast).

If there’s a change in what is being presented on a page because of an action taken, the screen reader is not informed of the change to the page. This doesn’t meet WCAG 2.1 success criterion 4.1.3 (status messages).

If error messages are displayed on a page, some of these can’t be read by screen reading software. This doesn’t meet WCAG 2.1 success criterion 3.3.3 (error suggestion).

Error messages remain on the page for a screen reader to read out when the user makes a change to the page. This doesn’t meet WCAG 2.1 success criterion 4.1.3 (status messages).

If someone is moved onto another page by actioning a button, they are not told of the change. This doesn’t meet WCAG 2.1 success criterion 4.1.3 (status messages), success criterion 2.4 (navigable) and success criterion 1.3.2 (meaningful sequence).

Data has not been displayed in a table, so understanding the relationship between parts of data is difficult. This doesn’t meet WCAG 1.3.1 (info and relationships).

We plan to correct these by September 2020.

When we publish new content we’ll make sure our heading structures meets 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.

This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value).

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on registered title information.

By September 2020, we plan to either fix these or replace them with accessible HTML pages.

The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

For example, we don’t plan to fix sasine deed information.

Any new PDFs or Word documents we publish will meet accessibility standards.

How we tested this website

This website was last tested on 21 August 2019. The test was carried out by Registers of Scotland.

We tested:

What we're doing to improve accessibility

We are centralising our accessibility roadmap and will provide this soon.

This statement was prepared on 19 September 2019. It was last updated on 19 September 2019.


Was this page helpful?