Accessibility Statement
Short answer: We want everyone to be able to read this site, including people who use screen readers, keyboards, or screen magnifiers. We aim to meet WCAG 2.1 Level AA: semantic structure, full keyboard access, a skip-to-content link, visible focus, color contrast that meets AA, and text that reflows and zooms. If anything is hard to use, email [email protected] and we'll fix it.
Our commitment
We want this site to be usable by everyone, regardless of ability or the technology they use. We work toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as our standard.
What we've done
- Semantic structure: real headings, lists, and landmark regions (header, navigation, main, footer) so assistive technology can navigate the page.
- Keyboard access: every link and control can be reached and used with a keyboard alone, and a "skip to content" link lets keyboard and screen-reader users jump past the menu.
- Visible focus: a clear outline shows where you are as you tab through the page.
- Color contrast: body text, links, and buttons meet or exceed the WCAG AA contrast ratio.
- Readable and flexible: text reflows and stays readable when you zoom to 200%, on phones as well as desktops.
- Calm by default: no auto-playing media, no flashing content, and we honor your system's "reduce motion" setting.
- Descriptive links and a page language set to English so screen readers pronounce content correctly.
- Works without JavaScript: the content is plain HTML, so it doesn't depend on scripts to be read.
Known limitations
Some pages include wide data tables that scroll sideways on very small screens. We're working to make those easier to read on phones. If you hit something that's hard to use, please tell us — real reports help us prioritize.
Tell us about a problem
If you have trouble using any part of this site, or you need something on it in a different format, email [email protected] with the page address and a short description of the problem. We aim to reply within about five business days and to fix genuine barriers as quickly as we can.
How we test
We check pages with keyboard-only navigation, verify color contrast against the WCAG AA thresholds, and review the underlying structure as pages change. Accessibility is ongoing, not a one-time box to tick, so this statement will be updated as the site evolves.