Accessibility statement

This statement covers RAMSReady at ramsready.co.uk, operated by Bloor Engineering Ltd.

Prepared and last tested: 9 October 2026.

How accessible this service is

We aim to meet WCAG 2.2 level AA. At the last test, automated checking found no failures on any of the pages listed below, in both light and dark colour schemes.

We are telling you plainly what that does and does not prove. Automated tools reliably check only a minority of the WCAG success criteria, mostly colour contrast, element naming and document structure. They do not judge whether the service makes sense when used entirely by keyboard, with a screen reader, or by somebody who finds dense text hard going. We have not commissioned an independent manual or user audit, so we do not claim full conformance. If you hit a barrier we have not found, we want to hear about it.

What we tested, and how

That round found and fixed real problems, including a switch with no name a screen reader could announce, body text and buttons below the contrast threshold, and a link in running text distinguished only by colour.

Known limitations

Reporting a problem

If you find something you cannot use, email george@bloorengineering.com and say which page and what happened. We aim to reply within 5 working days. If you need information from RAMSReady in a different format, such as large print, plain text or an accessible document, ask and we will provide it within 10 working days at no charge.

If you are a public sector customer

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 place the duty on the public sector body, not on its suppliers, so they do not apply to Bloor Engineering Ltd directly. We hold ourselves to the same standard so that you can rely on this service inside your own duty, and we will complete an accessibility conformance report on request. If you believe we have not responded properly to a request, the Equality Advisory and Support Service can advise you at equalityadvisoryservice.com.

What we are doing to improve

We re-run the automated audit when we change the interface, and we treat any contrast or naming failure as a defect rather than a nice to have. The next step we intend to take is a manual keyboard and screen reader pass, which is the gap this statement is honest about.