Legal
How this site is built to be used with a keyboard and a screen reader, what has not been tested, and how to tell us when something does not work.
No formal accessibility audit has been carried out on this site. This page is not a claim to meet a conformance level; it is a description of the work that has been done, each item of which can be checked against the site itself, and an honest list of what has not been done.
R&R Life Science Ltd — version 1.0, last reviewed 2 September 2026.
This comes first because it is what most people reading an accessibility statement actually need to know.
Each of these is a behaviour you can check on the site rather than a promise about it.
The first thing a keyboard reaches on every page is a link that jumps past the header and navigation straight to the page content.
The content area is itself focusable, so activating that link moves focus rather than only scrolling the page.
Moving between pages does not reload the document, so the name of the page you have arrived at is announced to a screen reader.
Anything reachable by keyboard shows a focus outline when it is reached by keyboard, and the outline is not removed for mouse users instead of being drawn properly.
If your device is set to reduce motion, the animated background, the carousel and the page transitions stop moving. This is honoured by every animated surface on the site, not only the obvious ones.
The product pop-out, the search panel and the application form use the browser’s own dialog element, so focus stays inside them while they are open and Escape closes them.
Controls are sized to be operable on a phone rather than sized to the text inside them.
The document is marked as British English, so a screen reader pronounces it correctly rather than guessing.
If part of the site fails, you get a page that still works — an explanation, a way to retry, and the main sections to move to — rather than an unstyled browser error.
Tables too wide for a phone scroll inside their own frame instead of forcing the whole page sideways.
Tell us what you were trying to do, the page you were on and what happened. If you use assistive technology, naming it helps — a fault is often specific to one combination of software.
There is no separate accessibility mailbox. Messages sent through the contact form reach the same place, and an accessibility report does not go to the back of the queue behind the rest.