This is the accessibility statement for the Welsh Revenue Authority (WRA) tax management system for Land Transaction Tax (LTT) and Landfill Disposals Tax (LDT).
This statement applies to the:
- Land Transaction Tax calculator
- Land Transaction Tax system
- Landfill Disposals Tax system
The Land Transaction Tax calculator allows customers and their agents to calculate any LTT due. The Land Transaction Tax system allows registered agents to submit returns for LTT. The Landfill Disposals Tax system allows landfill site operators to submit returns for LDT.
In this statement we refer to our tax management system as ‘website’. Our tax management system is accessed through the gov.wales platform. The Accessibility Statement for gov.wales contains information on the accessibility of our content on the gov.wales website and online forms. All our content which is essential to providing our services is accessible.
This accessibility statement explains:
- how accessible these services are
- what to do if you have difficulty using them
- how to report accessibility problems with the service
Using this website
This website is run by the Welsh Revenue Authority. We want as many people as possible to be able to use it. For example, that 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 these services using just a keyboard
- navigate most of these services using speech recognition software
- listen to most of the content using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
We know some parts of these services are not fully accessible:
- there is one accordion screen on the LTT system which keyboard-only users will find difficult to navigate. This screen contains an overview of the sections of the LTT return and enables you to access different parts of the tax return. Keyboard-only users will need help to navigate this page or can contact us for the return in an alternative format. Or alternatively, there is an accessible PDF version of the return online.
- on certain pages, headings are in an illogical order for keyboard-only and screen reader users
- the colour contrast ratio in some places does not meet the standard
- it is not clear when a notification of an error is displayed on some pages for screen reader users
- some radio buttons are inaccessible to JAWS users using Internet Explorer
- some page titles are not descriptive so it’s difficult to distinguish between them when using a screen reader
- the table on the LTT dashboard contains empty data cells which might be confusing for a screen reader.
We set out below our intentions to improve the accessibility of this website by September 2021 with some further discovery needed for some issues.
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille,
- email firstname.lastname@example.org
- call 03000 254 000
We’ll consider your request and get back to you in 10 working days.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of our services. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact the WRA Customer Experience team by emailing email@example.com
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).
Our helpdesk team is committed to providing extra help to customers who need it. If you need extra help when accessing our services call us on 03000 254 000.
If you experience difficulty contacting us by telephone, please use our online contact form and we’ll try to communicate with you via your chosen method.
Find out how to contact us.
Technical information about this website’s accessibility
The Welsh Revenue Authority 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 listed below.
The content listed below is non-accessible for the following reasons:
|Non-compliance area||Criteria not met||Resolution|
|Some elements on our forms are unlabelled. As a result, it will be difficult for screen reader or ZoomText users to determine the purpose of each form element.||This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).||We plan to fix this by May 2021.|
|There isn’t a warning that the system will sign you out after a period of inactivity||This fails WCAG 2.1 success criterion 2.2.1 (Timing Adjustable).||We need to do further research into this matter before we include this in our roadmap. We will do this research by December 2020 and will update this statement with our intended approach.|
|The heading structure is illogical in some areas and confusing for screen reader users.||This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).||We plan to fix this by May 2021.|
|Some of the links are inaccessible for keyboard-only users.||This fails WCAG 2.1 success criterion 4.1.2 (Name, Role Value).||We plan to fix this by May 2021.|
|The fieldset and Legend have not been marked up correctly on some pages which is unclear for screen reader users.||This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).||We plan to fix this by May 2021.|
|There is a missing ‘skip to content’ link, so people using a screen reader or a keyboard-only user are unable to bypass blocks of content.||This fails WCAG 2.1 success criterion 2.4.1 (Bypass Blocks).||We plan to fix this by May 2021|
|There is a duplicate ID on one of our pages which might make it difficult for screen reader users.||This fails WCAG 2.1 success criterion 4.1.1 (Parsing)||We plan to fix this by May 2021.|
|The tab order on some of our pages is illogical which can be difficult for keyboard-only users to interact with the page.||This fails WCAG 2.1 success criterion 2.4.3 (Focus Order).||We plan to fix this by May 2021.|
|The focus order on some of our pages is illogical affecting content being hidden for screen reader users on Android.||This fails WCAG 2.1 success criterion 2.4.3 (Focus Order).||We plan to fix this by May 2021.|
|Some links on pages have non-descriptive links which makes it difficult for screen reader users.||This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose).||We plan to fix this by May 2021|
|Some page titles are non-descriptive which makes it difficult for navigation.||This fails WCAG 2.1 success criterion 2.4.2 (Page Titled).||We plan to fix this by May 2021|
|Some radio buttons are not discoverable for users of JAWS software.||This fails WCAG 2.1 success criterion 4.1.1 (Parsing) and 2.1.1. (Keyboard).||We plan to fix this by May 2021.|
|Instructions on one page are not in the correct format which is confusing for users if an error message occurs.||This fails WCAG 2.1 success criterion 3.3.2 (Labels or Instructions).||We plan to fix this by May 2021.|
|Some data cells in a table are empty which can be problematic for screen readers users.||This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).||We plan to fix this by May 2021.|
|Some of the ascending/descending elements do not appear to be selectable to users of assistive technology.||This fails WCAG 2.1 success criterion 4.1.2 (Name, Role Value).||We plan to fix this by May 2021.|
|Some elements are not marked up correctly which is confusing for users using TalkBack on Android.||This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).||We plan to fix this by May 2021.|
|Some error messages are not notified to screen reader users.||This fails WCAG 2.1 success criterion 4.1.3 (Status Messages).||We plan to fix this by September 2021.|
|The colour contrast ratio in some places does not meet the standard which can affect some people’s ability to perceive the information visually.||This fails WCAG 2.1 success criterion 1.4.3 (Contrast) and 1.4.11 (Non-text Contrast).||We plan to fix this by September 2021.|
Not applicable. We are committed to improving the accessibility of our services and have a roadmap to meet the WCAG 2.1 AA standard by September 2021. However, some changes are still being assessed. We’ll update this statement when we undertake this research and have more information.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
We have one PDF (the LTT certificate) on the LTT service which is essential to providing our service. We need to do further research into this before we include this in our roadmap. We’ll do this research by December 2020 and will update this statement with our intended approach.
The accessibility regulations do not 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 do not plan to fix the payslip which is generated after submission of a return online as we don’t see this as essential to service.
Any new PDFs or Word documents we publish will meet accessibility standards.
What we’re doing to improve accessibility
Our accessibility roadmap below shows how and when we plan to improve accessibility on this website.
|Standard||Date standard met|
|WCAG 2.1 A standard||May 2021|
|WCAG 2.1 AA standard||September 2021|
Preparation of this accessibility statement
This statement was prepared on 15 September 2020.
This website was last tested on 11 November 2019. The test was carried out by Digital Accessibility Centre.
We tested a sample of pages, using the following approach to identify the sample:
- we considered the frequency of use of our services and prioritised the testing based on this, including the most common user journeys followed on our LTT system
- we considered the user base of our services and prioritised where the service was used by a wider variety of users more likely to use assistive technology
- we considered where we have previously received requests based on accessibility issues or assisted digital needs