Accessibility
An accessibility check that says what it cannot see
SiteRay runs the automated WCAG checks on any public page — contrast, labels, headings, alt text, landmarks — and reports each failure with the element that caused it.
Three audits every 24 hours with a free account. No card, and nothing switches off.
What it measures
Checked on every run
Automated checking finds roughly a third of accessibility problems. That is worth doing, because the third it finds is the third that is cheap to fix and embarrassing to leave. It is not an accessibility statement, and this page will not pretend otherwise.
Accessibility
Colour contrast, form labels, heading order, alt text, landmark structure and keyboard reachability — the automated half of WCAG, which is roughly a third of what a real audit covers and all of what a machine can check.
Colour contrast
Every text and background pair on the page against the 4.5:1 the standard asks for body text. The single most common failure, and the single easiest to fix.
Names and roles
Buttons, links and form fields with nothing a screen reader can announce — an icon button with no label is a dead end for somebody who cannot see the icon.
Structure
Heading order, landmark regions, page language and whether the document has a title.
How it works
Three steps, about ninety seconds
Paste the address
Any public page. The engine resolves it, follows redirects and reports where it ended up.
It loads the page twice
Once at a phone viewport on a throttled connection, once on a desktop, in a real browser — not a lookup against a database of old crawls.
You get numbers, ranked
Four scores, the measurement behind each, and the problems in the order they are costing you. Results stay in your dashboard, so a re-run shows what moved.
Questions
What this does, and what it does not
- Does passing this make my site accessible?
- No. Automated tools catch about a third of WCAG failures, and none of the ones that need judgement: whether alt text is *useful*, whether a flow can be completed with a keyboard, whether an error message makes sense. A clean automated result is the floor, not the ceiling.
- Is this enough for an accessibility statement or an EAA obligation?
- No. A statement has to be based on an evaluation of the whole service against the standard, including manual and assistive-technology testing. Use this to clear the automated failures first so a human audit spends its time on what only a human can judge.
- How does the audit actually run?
- We load the page in a real browser twice — once on a simulated mid-range phone on a slow connection, once on a desktop — and record what happens. Nothing is estimated from a database of past crawls; every number comes from that load, on the day you asked for it.
- Is it free?
- Yes. Three audits every 24 hours with a free account, which exists so the engine is not run by scripts. There is no card, no trial, and nothing switches off.
Measure it now
One address, ninety seconds, and a list you can hand to whoever builds the site. If the list turns out to be longer than an afternoon, that is a conversation we are happy to have.