Readable, operable, and honest about the rest.
This statement covers guardstate.co, the website. The target is WCAG 2.2 at level AA. Below is what has been done, what falls short today, and where to send a problem so that it gets fixed rather than filed.
What has been done.
Each of these was checked on the built pages, in both themes, not assumed from the code.
Contrast, measured
Text and interface colours were measured against their own backgrounds in the light theme and again in the dark theme, and every pairing used for body text meets the AA ratio in both.
The site follows your system setting by default, and the theme control in the footer overrides it in either direction. Nothing is carried by colour alone: a status is always also a word.
Reachable by keyboard
Every link, button and control can be reached and operated from a keyboard, in the order the page reads. The focus ring is drawn in the accent colour, offset from the control so it is visible against both grounds, and it is never suppressed.
A skip link is the first thing focus lands on, and it jumps straight to the main content past the navigation bar. Interactive elements are real buttons and links rather than styled boxes, so they behave the way assistive technology expects.
Motion, reduced on request
If your system asks for reduced motion, the site honours it. Entrance transitions are removed, the rolling line in the cookie notice is set out in full instead of scrolling, and the hero clip is never attached or fetched at all: the still photograph is the whole of the hero.
There is no parallax, nothing flashes, and nothing moves faster than three times a second.
No sound, no interruption
Nothing on this site plays audio. The hero clip is muted, has no audio track in use, and loops quietly behind the text.
Nothing pops up over what you are reading. There is no interstitial, no newsletter overlay and no chat widget. The cookie notice is a notice rather than a gate: one line, one button, and nothing behind it is blocked while it is open.
Text that behaves
Type is set in relative units, so browser zoom and your own font size work normally, and the layout reflows to a single column on a narrow screen without a horizontal scrollbar. Tables scroll inside their own frame rather than dragging the page sideways.
Headings are in order, landmarks are labelled, images carry alternative text that says what is in them, and the language of the page is declared as British English.
What falls short today.
Written down because a statement that lists only successes is not a statement.
The demonstration preview
The example portal on the main page is a simulation of the application, built to be looked at rather than used. It is driven by scripted steps, its data is a synthetic example tenant, and it is not held to the same keyboard and screen reader standard as the rest of the site.
Nothing on the site depends on it. Everything it shows is also described in words nearby, so a reader who skips it loses no information. The application itself will have its own accessibility statement, written against the real thing rather than a picture of it.
The hero clip
The clip at the top of the main page starts by itself and loops. It respects a system request for reduced motion, and with that setting on it never loads at all, but there is no button on the page to stop it for someone who has not set that preference. That control is on the list to add.
The clip carries no information that is not in the words beside it, and it has no audio.
Third-party fonts
Two typefaces load from Google Fonts, and the display typeface loads from this site. If any of them is blocked or slow, the page falls back to a system stack and stays readable, but the line breaks and the rhythm will differ from what is described here.
The display typeface is drawn narrow at large sizes. It is used for headings only, never for body text or for any control label.
What has not been tested
This statement is based on our own checking, not on an independent audit, and not on testing with disabled users.
If you find something this page claims and your own experience contradicts, your experience is the fact and this page is the error. Tell us and we will correct both.
Telling us about a problem.
The fastest route to a fix, and what happens after you send it.
Where to writeenquiries@guardstate.coWhat helpsThe page address, what you were trying to do, the browser and any assistive technology you were using, and what happened instead.What we doWe reply as soon as we can, and we treat access problems as bugs. We say what we can fix and when, and if something cannot be fixed we say why and offer another way to get the same thing.If you need something on this site in another format, ask. We would rather send you a plain document than leave you locked out of a page.
This statement was prepared on 23 September 2026 from our own review of the site. Last updated 23 September 2026.
The rest of the site.
What the product does, what it costs, and what runs on your devices.