Accessibility statement

This statement is about the rTraining website, the training platform run by rTriibe. It sets out the standard we are working to, what already works, what does not work yet, and how to report a barrier.

We treat accessibility as a requirement. Compliance training is often mandatory, which means somebody has to complete it whether or not the software suits them, so a barrier here matters more than a barrier on a shopping site.

Our target

We aim to meet WCAG 2.2 level AA. rTriibe has a duty under the Equality Act 2010 to make reasonable adjustments for disabled people, and WCAG 2.2 AA is how we measure ourselves against it. This statement follows the format of the public sector accessibility regulations as good practice, although as a private company we are not bound by them. It is also the standard a school, trust or local authority will ask us about when it buys training, because those regulations do bind them.

The platform is partially conformant with WCAG 2.2 AA. Partially conformant means most of the platform meets the standard and the exceptions are listed below. We have not yet had the platform independently audited, and we are not claiming full conformance until an audit says so.

What works

• Keyboard. Every control can be reached and operated with a keyboard alone, in a sensible order. Dialogs trap focus while open, close on Escape, and return focus to whatever opened them.
• Visible focus. There is always a visible focus indicator, and it is never removed. It is high contrast against every background we use.
• Target size. Anything you tap or click is at least 24 by 24 pixels, the AA minimum, including small chips and table row controls where the drawn button is smaller than its target.
• Every course can be completed in silence. The written text is the course. Narration is a second rendering of the same words, so nobody has to hear anything to pass. Narrated sections carry captions and a full transcript.
• Text, not images of text. Course content is real text, so it reflows, responds to your browser's text size, and can be read by a screen reader. Course cover images are abstract illustrations; each carries a short text alternative that says so and names the course, and none of them carries information the page does not also give in words.
• Contrast. Body text, interface text and interface borders meet the AA contrast ratios. Colour is never the only way information is conveyed: a status always carries a word as well as a colour.
• Reduced motion. If your device asks for reduced motion, animation is reduced to a single fade and smooth scrolling is turned off.
• Zoom and reflow. The platform works at 400% zoom and at a 320 pixel viewport width without two-dimensional scrolling, except where noted below.
• Reading level. Course text is written for a general adult audience and each section records its reading age, so we can find and rewrite the sections that drift.
• No time limits. Nothing expires while you read a section, and no assessment is timed.
• Sensible page structure. Real headings in order, real lists, real tables with header cells, one main landmark per page, and a page title that says where you are.

What does not work yet

We have listed the areas where the platform does not currently meet the target standard.

• Wide tables scroll sideways. The compliance and evidence tables in the organisation area scroll horizontally on a narrow screen. They are keyboard scrollable and readable with a screen reader, but that is not the reflow behaviour WCAG 1.4.10 asks for. We plan a card view for narrow screens. The fix has no date yet, and we will update this statement when it does.
• Downloaded PDFs are not tagged. Certificates, and evidence packs downloaded as PDFs, are not yet tagged, so a screen reader may not read them in a sensible order. The same information is available as HTML in your account, evidence packs can also be downloaded as a spreadsheet file (CSV), and we will send a certificate in another format on request. Tagging has no date yet, and we will update this statement when it does.
• The narration player's progress may not announce well everywhere. The platform has not yet been tested with a full range of screen readers. Narration is optional throughout, so nothing depends on it.
• Payment pages are Stripe's. Their accessibility is Stripe's to state, not ours. If you cannot complete a payment, tell us and we will invoice you instead.
• A few older course sections. Sections written before our current authoring rules may have images with weak alternative text. Tell us which course and we will fix that one first. The older sections have not yet been audited one by one, so we cannot yet say how many are affected.

Content we do not control

Pages on other sites that we link to, such as a regulator's own guidance, are theirs to make accessible. If one of them stops you completing a course, tell us and we will give you what you need from it another way.

Reporting a barrier

If something on this platform stops you, tell us. Please describe the specific barrier you hit, because a specific report is what we can find and fix.

• Email: training@rtriibe.com, with "accessibility" in the subject line
• Post: RTRIIBE LTD, Level One Basecamp Liverpool, 49 Jamaica Street, Liverpool, England, L1 0AH
• Phone: we do not have a phone line, but if writing is difficult for you, tell us and we will call you.

Helpful to include, if you can: the page you were on, what you were trying to do, what happened, and what you were using, such as your browser, screen reader, magnifier or switch device.

We will acknowledge within 5 working days, the same time our complaints procedure sets, and tell you what we are going to do and when. If a fix will take time, we will offer a way to get the training done in the meantime, including doing it with a person over the phone if that is what it takes. Nobody should fail to complete mandatory training because our software did not suit them.

If we do not get it right

If you are not happy with our response, you can use our complaints procedure. For advice about your rights under the Equality Act 2010 you can contact the Equality Advisory and Support Service. If you are in Northern Ireland, contact the Equality Commission for Northern Ireland.

How we test

• Our own team tests as we build. rTriibe's own team checks each feature against the standard above as it is built.
• Automatic checks. Our code checker flags some accessibility faults, such as an image with no text alternative or an invalid ARIA attribute. We do not yet run a dedicated automated accessibility checker on the whole platform.
• Screen readers. The platform has not yet been tested with a full range of screen readers.
• Independent audit. We have not yet commissioned an independent audit. When we do, we will update this statement.

Dates

• This statement was prepared on 24 September 2026.
• It was last reviewed on 29 September 2026.
• The platform is tested by rTriibe's own team as features are built. It has not yet been tested independently.
• Next scheduled review: 29 September 2027.

We review this statement at least every twelve months, and whenever we ship something that changes how the platform is operated.