All Collections
Getting Started
Welcome to WeTrack!
Accessibility in WeTrack
Accessibility in WeTrack
Charlie Vaughan-Fowler avatar
Written by Charlie Vaughan-Fowler
Updated over a week ago

Accessibility statement for WeTrack

This accessibility statement applies to the WeTrack application, which we want as many people as possible to be able to use.

How accessible this application is

We know some parts of this application are not fully accessible:

  • the text will not reflow in a single column when you change the size of the browser window

  • you cannot modify the line height or spacing of text

  • keyboard navigation may not be possible in some places

  • navigation using a screen reader may not be optimal in all places

  • some buttons and text may not have adequate contrast in some places

Feedback and contact information

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

We’ll consider your request and get back to you in 10 working days.

You do not need to give us details of your disability or accessibility need as part of your request.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of the WeTrack application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact:

You do not need to give us details of your disability or accessibility need as part of your request.

Technical information about this website’s accessibility

Compliance status

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

Non-accessible content

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

Non-compliance with the accessibility regulations

Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

  • We plan to resolve this by February 2022. When we publish new content we’ll make sure our use of images meets accessibility standards.

Some elements (such as buttons and text) do not have sufficient contrast. This fails WCAG 2.1 success criteria 1.4.3 (contrast minimum) and 1.4.11 (non-text contrast).

  • We plan to resolve these by February 2022. When we publish new content we’ll make sure our use of contrast meets accessibility standards.

It is sometimes not clear when focus is applied to elements, or the order in which focus can be applied, or how to remove focus. This fails WCAG 2.1 success criteria 2.4.3 (focus order) and 2.4.7 (focus visible).

  • We plan to resolve these by August 2022. When we publish new content we’ll make sure our use of focus meets accessibility standards.

Some elements are not programmatically determinable, meaning they are not readable by Screen Reader. This fails WCAG 2.1 success criteria 1.3.1 (info and relationships), 2.5.3 (label in name) and 4.1.3 (status messages).

  • We plan to resolve these by February 2022. When we publish new content we’ll make sure semantic coding and programming meets accessibility standards.

It is not possible to navigate to or away from certain elements using the keyboard. This fails WCAG 2.1 success criteria 2.1.1 (keyboard) and 2.1.2 (no keyboard trap).

  • We plan to resolve these by August 2022. When we publish new content we’ll make sure keyboard navigation meets accessibility standards.

Some links are not properly described by the link context alone. This fails WCAG 2.1 success criterion 2.4.4 (link purpose in context).

  • We plan to resolve this by August 2022. When we publish new content we’ll make sure link context meet accessibility standards.

There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option). This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

  • We plan to resolve this by August 2022. When we publish new content we’ll make sure bypass blocks meet accessibility standards.

What we’re doing to improve accessibility

The development of the WeTrack application is subject to regular accessibility reviews and places accessibility at the heart of its design process. Regular audits and reviews are undertaken to assess where gaps lie and to plan improvements.

Preparation of this accessibility statement

This statement was prepared on Thursday 26th August 2021. It was last updated on Tuesday 31st August 2021.

This website was last tested on 16th August 2021. The test was carried out by WeTrack Software.

Did this answer your question?