Accessibility
Accessibility
A meaningful share of the people reading this are in their eighties, or are reading it at eleven at night after a hospital visit. Both deserve a page that behaves.
The standard
This site targets WCAG 2.2 Level AA.
What is enforced rather than intended
Some of it is checked automatically every time the site is built, and the build stops rather than publishing a page that breaks one of these:
- Every image has real alternative text. Not a filename, and not empty.
- One first-level heading per page, so the outline a screen reader announces is the outline that was intended.
- Colour is defined in one place and every combination in it was measured against the AA contrast requirement before it was used. Body text sits at roughly 12.9 to 1 against the background, well beyond the 4.5 required.
The point of checking these in the build is that intentions decay. A rule that is only written down survives until somebody is in a hurry.
The rest of it
- Text is 18 pixels as a floor, not a default, and it scales with your browser or system setting. Nothing here is pinned to a fixed size.
- Everything works from a keyboard, and the focus outline is deliberately loud rather than tasteful.
- Touch targets are at least 48 pixels, and 64 for anything primary, which is a genuine difference for hands that are not steady.
- The colour is never the whole message. Anything indicated by colour is also indicated by a word.
- Motion is minimal, and what little there is honours a reduced motion preference.
- It works without JavaScript. Every page is plain HTML. The menu and the form work either way.
- No carousels, no popups, no interstitials, and nothing that moves on its own.
Where it is imperfect
Stating this plainly is more useful than a claim of full conformance, which almost nobody can honestly make.
- The site has been tested with VoiceOver on macOS and iOS. It has not yet been tested with JAWS or NVDA, so there may be announcement quirks we have not found.
- The navigation menu uses expanding panels. They are keyboard operable and announce their state, but a simple list would be simpler still, and that is a fair criticism.
- Long explanatory pages are long. Headings and a consistent structure help, but there is no getting around the fact that some of this is dense reading for somebody who is exhausted.
Telling us
If something here does not work for you, please write to [email protected] and describe what happened. Tell us the page and roughly what you were using if you know it, and if you do not know, tell us anyway.
We would rather hear about it plainly than have somebody quietly give up on the page, and a report about a real barrier is treated as a defect rather than as feedback.
Last reviewed 29 July 2026
The part that does not end
One plan finishes. The driving, the meals and the appointments do not.
Follow-through closes out a single plan and then stops, on purpose. The ongoing work of a family sharing care is a different job: who is taking him on Thursday, who is picking up dinner, who is quietly doing all of it. That is what Family Observatory is for.