Accessibility statement

This statement covers this website. Accessibility requirements for future pilot projects would be defined in scope using Accessibility.

What this site targets

WCAG 2.2 AA on every page. Automated rule checks run against every route in the sitemap on each pull request, and a nightly sweep repeats them across the whole site. A violation fails the build rather than becoming a ticket for later.

What that testing does and does not cover

Automated rules catch a minority of real barriers. Keyboard-only traversal and screen-reader review are also required. Where the site has not been directly tested with people who use a particular assistive technology, rhizae does not claim that level of validation.

What is supported

Keyboard. Every page starts with a skip link that jumps past the header, sidebar, and search to the main content. Focus is visible on every interactive element, including links in body text, and moving focus to the main content actually moves it rather than only scrolling the page.

Contrast. The default palette targets AA contrast. Beyond that, the theme panel offers three demonstration tiers that raise contrast further, strengthen the focus indicator, and enlarge minimum target sizes. In Windows high contrast mode, borders and focus outlines are drawn in the system color rather than a fixed palette, so nothing is distinguished by color alone.

Motion. Animation is reduced automatically when the operating system asks for it, and there is an in-app preference for the same thing, so a visitor can turn motion down without changing a system setting.

Readability. Body text sits on a measure of roughly 68 characters, which keeps a reader from losing their place between lines. Text is sized in relative units and survives browser zoom and larger default font sizes, and one demonstration tier applies the line height, letter spacing, word spacing, and paragraph spacing named by WCAG SC 1.4.12 Text Spacing.

Known limitations

These are current and stated plainly rather than left to be discovered.

• The site has not been tested with people who use screen readers or other assistive technology as their primary means of access. Automated checks and keyboard review are not a substitute for that, and the claim is limited accordingly.
• Site search, the theme and accessibility panel, the analytics consent banner, and the mobile navigation overlays require JavaScript. All page content is prerendered and readable without it, and navigation between pages is plain links, so nothing written here becomes unreachable. The search and the panel do become unavailable. The consent banner not appearing costs a visitor nothing, since without JavaScript there is no analytics to consent to.
• No formal third-party accessibility audit has been carried out.

Reporting a barrier

If something here blocks you, tell us through the contact page. A report is treated as a defect rather than a feature request, and we will say what we intend to do about it and when.

Why this sits in the open rather than in a compliance appendix is covered in our position on access.