Accessibility statement

About this statement

This statement is about the uFTi documentation website and the PDFs on it. It is not about the uFTi app. Each manual describes the accessibility features of the app where it covers them.

Oughtibridge Ltd runs this website. We want as many people as possible to be able to use it. We used the layout of the GOV.UK accessibility statement as a guide.

What we aim for

The web pages aim to meet WCAG 2.2 level AA. These are the international rules for accessible web pages. The site is built with components from the GOV.UK Design System. They give every page headings, landmarks, a skip link, clear focus marks and enough contrast.

The PDFs aim to meet PDF/UA-1. This is the standard for accessible PDFs. Each PDF has a structure that a screen reader can follow.

We chose the colours and the fonts of the site for clear reading. We check that every pair of colours in our theme has enough contrast.

The words are written for a reader of about 11 years old.

What we check

These checks run by machine on every change to this site. A change that fails one of them cannot be merged.

Table 1. Checks that run by machine
Check	What it finds
axe-core	Problems against WCAG 2.2 level AA, on every page of the site, in a real browser. We allow no exceptions.
Nu HTML Checker	Pages with faulty code. Each page must have one main heading and one main area.
Theme check	Pairs of colours that do not have enough contrast.
veraPDF	PDFs that do not meet PDF/UA-1. For now it checks the PDFs of the Windows and Android phone manuals.
Font check	PDFs where a font is not stored inside the file.
Picture check	Pictures with no alternative text. Every picture has it.
Reading level	Text that is too hard. The writing is measured for reading level.

What we have not done

A person outside our team has not audited this site. Machine checks find only some problems, so we do not say that the site meets every rule.

We have not recorded any testing with screen readers or other assistive technology. We plan to test with them before each release. When we do, we will say here what we found.

Known limits

The pictures of the app are screenshots of its screens. Each has alternative text that says what it shows. The words inside a screenshot are part of the picture.
The manuals are written in British English only.
The PDFs of some manuals are not yet checked by veraPDF.

Ask for another format or tell us about a problem

Each manual and Quick Start is on the website and in a PDF. If you need another format, or if you find a barrier, tell us.

Use the issue form on our GitHub page. Anything that you write there is public. Do not put private details in it.

Tell us the address of the page, what went wrong and what you were using. Tell us the format that you need. We will look at each report.

About the date of this statement

We wrote this statement on 25 October 2026. It describes the checks that we run on that day. We will change it when the checks change.

Words we use

Alternative text: A short written description of a picture. A screen reader reads it aloud.
Assistive technology: Tools that help people use a computer, such as a screen reader.
Contrast: How much one colour stands out from another. Text needs enough of it to be read.
PDF/UA: The international standard for PDFs that people with disabilities can use.
Screen reader: A program that reads what is on the screen aloud.
WCAG: The Web Content Accessibility Guidelines. Level AA is the level that most laws and policies ask for.