Accessibility
Accessibility statement
This statement applies to https://point28.co.uk. It is written to the same standard we hold client work to, and it lists what this site does not yet meet alongside what it does.
How conformant is this site?
This site aims to conform to WCAG 2.2 level AA. Based on our own testing it meets that standard, with the exceptions listed below. That assessment is self-made, not independently audited, and the distinction matters — see the limitations section.
What has been tested and met?
- Text and background contrast measured against the colour actually painted behind each element, not against an assumed background. 417 text nodes checked, zero failures at AA.
- Every interactive control reachable and operable by keyboard alone, with a visible focus indicator that stays visible on coloured backgrounds.
- Content readable and operable at 200% zoom, because type is set in relative units with a floor rather than in raw viewport units.
- prefers-reduced-motion honoured as the absence of motion. Under that setting the animation library writes no inline style to the page at all.
- Every page usable with JavaScript disabled: content, links and navigation are identical.
- One h1 per page, no skipped heading levels, and landmarks present on every page.
- Decorative imagery carries empty alt text so screen readers skip it rather than announcing meaningless descriptions.
What is not yet conformant or not yet tested?
No independent third-party audit has been carried out.
Everything above is self-tested with a keyboard, a screen reader and automated tooling. Automated checks reliably catch only around a third of real barriers, so self-assessment is a floor and not a substitute for an external audit.
The scrolling sequence on the home page has not been tested with every assistive technology.
It is decoration: it carries no information, is hidden from assistive technology, and is replaced by a single static image under reduced motion or if it fails to load. But the range of AT combinations tested so far is limited.
Cognitive accessibility has not been formally assessed.
Language is kept plain and jargon is defined on first use, but no structured readability or cognitive-load testing has been done.
How was this tested?
A manual pass with a keyboard and a screen reader, plus automated checks run against the production build rather than a development server. Contrast is measured programmatically against the background actually rendered behind each element, at six device profiles including both iPhone heights — with the URL bar showing and collapsed, because layouts break between the two.
How do I report a problem?
If something on this site is not usable for you, please tell us — a specific description of what you were trying to do and what happened is the most useful thing you can send. Email krish@point28.co.uk and you will get a reply within one working day.
We aim to fix reported barriers rather than explain them away. If we cannot fix something, we will say so here and say why.