What was tested,
and what still falls short.

This site aims to meet WCAG 2.2 level AA. It was last tested on 5 August 2026 and the next review is due by 5 August 2027.

What was tested, and how

• An automated pass with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rulesets, on all nine pages. It reports no violations. The script is in the repository and runs against the built site, so the test is repeatable rather than a one-off claim.
• A keyboard-only pass through every page and the enquiry form — tab order, a visible focus indicator on every stop, no keyboard traps, and the skip link as the first stop.
• Heading order checked on every page: one h1, no skipped levels.
• Colour contrast measured against the brand’s own palette rather than eyeballed, on every background the site uses. Two of the brand’s colours do not clear AA as small text on every ground — the supporting grey on any of them, and the accent gold on the tinted ones — so neither is used that way here. The accent survives as rules and underlines, where no contrast minimum applies.
• The audit measures the settled page: it waits for the webfonts and switches off the fade-in animation first. Testing mid-animation was reporting a pass on content that had not finished rendering, and hiding four real contrast failures behind elements the checker skipped while they were still transparent.
• Form labels, required fields and error messages checked for correct association — each error is written into the field’s own accessible description, so it is announced rather than only shown, and it carries a word rather than only a colour.
• Rendered with reduced-motion preferred, to confirm nothing stays hidden behind an animation.
• No third-party requests. The typefaces are served from this site, so nothing about a visit is disclosed to anyone else.

What is known to fall short

Everything below is a real limitation of this site as it stands today. A statement claiming no known issues, on a site nobody has tested, is worse than no statement at all.

• It has not yet been tested with a screen reader by a person.

  The automated and keyboard passes above are real and repeatable, but they are not the same as somebody using the site with VoiceOver or NVDA. That pass is scheduled, and anything it finds will be listed here.

Reporting a problem

If you find something on this site you cannot use, tell me and I will fix it. Email hello@bowerswebdesign.co.uk. I will acknowledge within one working day and tell you what I am going to do about it.

hello@bowerswebdesign.co.uk

What this means if I build for you

The same standard applies to your build: accessibility is designed in from the start rather than tested for at the end, and you get a written statement like this one for your own site — what standard, what was tested, when, and what is outstanding. On the Assured care plan it is reviewed and rewritten every year.

If you are a public sector body, note that the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 set out what your statement must contain and where it must sit. I will build to that format where it applies to you.