Accessibility

Last updated: 18 September 2026

What we are aiming for

We aim to meet the Web Content Accessibility Guidelines version 2.2 at level AA. We believe this site is partially conformant: it was designed and built to that standard and we have measured the parts we could measure, but it has not been independently audited, so we are not claiming full conformance.

This site is about remembrance and fundraising. The people using it are often doing so at the worst moment of their lives, sometimes on an old phone, sometimes with tears in their eyes. That is the reason for the care described below, rather than a compliance exercise.

What is built in

• Skip to content. The first thing a keyboard reaches on any page is a link that jumps past the navigation.
• A visible focus ring on everything you can reach with a keyboard, which changes colour on dark backgrounds so it stays visible. The ring on the teal header measured 1.6:1 against it, short of the 3:1 that WCAG 2.4.11 asks for, so it is drawn in white there instead.
• The menu on small screens is a native browser control, so it opens, closes and announces its state correctly without JavaScript. Pressing Escape closes it and returns you to the button you opened it with.
• Reduced motion is respected. If your device is set to reduce motion, the animated light in the header stops, drifting particles are removed, smooth scrolling is turned off and transitions are reduced to almost nothing.
• The page works without JavaScript. Styles still load, the navigation still opens, search still works and the revenue calculator still produces correct figures - the server does the arithmetic instead of your browser.
• Typefaces are served from our own servers, with a matched fallback, so text does not jump about while a font loads on a slow connection.
• Decorative graphics are hidden from screen readers and images that carry meaning have text alternatives.
• The calculator announces its results as they change, so they are not silently updated for someone using a screen reader.
• The cookie banner does not trap you. It has no overlay and does not block the page - you can ignore it entirely and read the site - and refusing is exactly as easy as accepting, with both buttons the same size and weight.

Colour contrast, measured

We changed the brand colour during the build because the original did not pass. The figures below are our own measurements, not an audit:

• Brand teal on white: 6.74:1, against the 4.5:1 that AA requires for body text.
• Navigation links through the semi-transparent header: 5.27:1 (they were 3.43:1 before the change).
• The "Get started" button: 6.05:1 (it was 4.11:1).
• The small print in the footer: 4.6:1 - a pass, but with little room to spare.

Where we know we fall short

We would rather list these than let you discover them:

• No independent audit. Everything above is our own testing.
• We have not tested with screen readers, at 200% zoom, or against the reflow requirement, so we cannot make claims about any of them.
• The header animates continuously unless your device asks for reduced motion. There is no button on the page to stop it, which may not satisfy WCAG 2.2.2 for everyone who needs it.
• The footer's legal text is small, at 11 pixels. It passes for contrast, but it is smaller than we would like.
• Which page you are on is marked with JavaScript. Without it, the current section is not indicated in the navigation.

Tell us

If something here stops you doing what you came to do, please tell us - it is the fastest way for it to get fixed, and we would rather hear it than not.

Email [email protected]. Say which page, what you were trying to do and what happened. We aim to reply within five working days.

If you are not satisfied with our response, you can contact the Equality Advisory and Support Service at equalityadvisoryservice.com.

About this statement

This statement applies to getluminary.co.uk. It was prepared on 18 September 2026 based on our own testing of the live site.