Accessibility
Accessibility
A lot of the people this site is for are older, disabled, or both. That shaped how it was built rather than being checked at the end.
What we did
Body text is 17–18px with generous line spacing, and nothing important is set in small gray type. Color combinations are checked against WCAG 2.2 AA, including hover and keyboard-focus states — by hand, against a live page, rather than by the build. Narrower checks are automated: that form fields keep a visible edge, that grouped questions keep their labels, and that the page avoids a grid-sizing pattern that can stop a layout reflowing when text is enlarged. Where a test browser is available, the resource lists are also checked for text overlapping itself, at seven screen widths from 320px up.
Everything works from the keyboard, and the focus outline is deliberately obvious rather than subtle. Links and buttons are large enough to hit without precision. Form fields have real labels, not placeholder text that vanishes when you start typing, and errors are described in words rather than signaled only by color.
The layout reflows to a single column on a phone and survives being zoomed to 200% without losing content. If your system asks for reduced motion, the small amount of animation here turns off.
What we have not done
This site has not been through a formal audit by a third party, and it has not been tested with every screen reader. Some of our checks are automated and some are done by hand — the color audit of a live page is one of the hand-run ones. So a change could make something here harder to read before the next audit catches it. If you find anything difficult to read, please tell us on the contact page.
If something does not work
Please tell us, and say what you were using. We would rather fix it than have you work around it. A page that is hard for you to read is our defect, not your problem.
Getting around on the day
The event is in a warehouse. It has a ground floor and offices upstairs, and there is no elevator. Everything you need is planned for the ground floor — where you arrive, the organizations, and sitting down one to one with someone about your benefits. The offices upstairs are extra rooms for those conversations when the ground floor is busy, not the only place they happen.
One thing to be straight about, because the paragraph above could be read too kindly: the rooms with doors are upstairs. A ground-floor conversation happens on the warehouse floor rather than behind a closed door, so it will not be as private. We would rather tell you that now than have you find it out when you sit down to talk about your claim.
We are telling you all of this now rather than on the day, because whether a building has an elevator is the kind of thing you want to know before you decide to come. If stairs are a problem for you, say so on the registration form, and if you meet with a service officer, the conversation happens downstairs. The same field is where to say that a private conversation matters to you. That is what it is for.
What we are not going to claim: we have not measured the doorways, and we are not promising accessible parking, accessible toilets or a hearing loop, because nobody has checked and we are not going to guess about something you would travel for. If one of those decides whether the day works for you, ask on the contact page and we will go and find out rather than reassure you.
If you need the event to work a particular way — wheelchair access, a hearing loop, a quieter space, a service animal — there is a field for exactly that on the registration form, and we would rather know in advance than improvise on the day.
