Accessibility Statement.
We want both sites to be usable with a keyboard, a screen reader, a magnifier, or none of those. This says what we have built, what we have measured, and what we have not checked.
What This Covers
This statement covers boothroydgroup.com and boothroyddistribution.com. One company operates both, they are built from the same code and they serve the same stylesheet, so it is the same statement on each and it is published on each.
It does not cover the Cellular Path app or the Cellular Path web portal that come with the product. Cellular Path runs those under its own terms.
The Standard We Build To
We build to the Web Content Accessibility Guidelines 2.2 at level AA.
We have not had an independent audit, so this is an account of what we built and tested, not a certified conformance claim. Where we have not tested something it is listed below rather than left to look like a pass.
How The Sites Are Built
- Neither site runs any JavaScript. The only script tags on either are structured data for search engines, which a browser does not execute.
- The index in the header opens with a link and a CSS selector, so it works with scripting turned off.
- Fonts are served from the site itself. There is no content delivery network, no analytics, no advertising and no tracking script.
- Neither site sets a cookie, so there is no consent banner in the way.
- The first thing a keyboard reaches on every page is a skip link to the main content.
- Every page has one h1, and its headings run in order with no level skipped.
- Every image carries alt text. The build fails if one does not.
- Every image is served with its width and height, so the page does not move under you while it loads.
- Keyboard focus is visible: a two pixel green outline, offset from what it is on.
- A paragraph is capped so that it never runs the width of the window. On how-we-work on boothroydgroup.com, in a 1280 pixel window, the paragraph box measures 660 px and a line averages 74 characters.
What We Measured
Target heights and widths were measured in Chromium on the built pages at 320 and 360 pixels, not read off the stylesheet. Page weight and the width of a paragraph were measured at 1280 pixels. Contrast ratios are calculated from the six colour values in our brand standard. That calculation runs in the build, and it is checked against a published reference figure before any of ours is trusted.
What We Have Not Checked
- No independent audit, and no testing by a group of disabled users.
- Neither site has been tested with a screen reader.
- Neither site has been tested in Safari, Firefox, or on iOS or Android. Everything above was measured in Chromium.
- Neither site has been tested in Windows High Contrast mode or with forced colours.
- There is no dark colour scheme. Both sites render on a pale ground whatever the system is set to.
- Target heights were measured at 320 px and at 360 px and nowhere else. The 44 px boxes are set inside a phone breakpoint, so above 960 px a link takes the height of its own text instead. We have not measured what that comes to, so the target figure above is a phone figure and is not a claim about a desk.
- The footer was left out of the target measurement at both widths. It is a block of index links rather than a row of thumb targets, and the 44 px boxes were never applied to it.
Known Problems
- The skip link is 26 px high on every page of both sites. It is the first thing a keyboard reaches and it is only visible once it has focus.
- A link that sits inside a sentence is as high as the line it is on, which is about 20 px. In the measurement that is the link to the privacy notice inside the trade application form, 40 px at 360 px and 18 px at 320 px, and the links out to Ofcom in one of the installer questions, 20 px at 360 px.
- Neither kind is a failure. The guidelines ask for 24 px, which the skip link clears, and they exempt a link whose size is set by the line height of the text around it, which the links in sentences are. They are written down here rather than left for you to find.
Telling Us About A Problem
Write to hello@boothroydgroup.com. Tell us the address of the page, what you were trying to do and what happened. If you use assistive technology, tell us which one and which browser.
That address reaches an engineer rather than a queue. We do not publish a target for how quickly it is answered, because the desk is one person and a target we cannot hold is worse than none.
If you need anything on either site in a different form, ask and we will send it.
How This Statement Was Prepared
Prepared by Boothroyd Group Limited on 24 October 2026 by testing the built pages ourselves. It has not been reviewed by an external auditor. It is revised when either site changes.
Contact
Tell Us What Must Not Fail.
One address. It reaches the principal, not a queue. There is no switchboard and no chat widget.
hello@boothroydgroup.com