Skip to the main content
ClandrixClandrixSite Search
DonateBuy MerchMerch

Accessibility

Site Search is built to be usable by as many people as possible. The target is WCAG 2.2 level AA. This page lists what is in place and what is not, so you can judge it for yourself rather than take a badge on trust.

What is built in

  • Every control can be reached and operated with a keyboard, and the focus outline is always visible.
  • A skip link is the first thing keyboard focus lands on.
  • An accessibility panel offers dark, light, and high contrast colours, four text sizes, wider reading spacing, permanent link underlines, motion off, and a thicker focus outline.
  • The same panel offers colour vision filters for protanopia, deuteranopia, tritanopia, and full colour blindness.
  • Colour is never the only way information is given, and text meets contrast requirements against its background in every theme.
  • The layout reflows without a horizontal scrollbar down to 320 pixels wide and at 200 percent zoom.
  • Text can be resized by your browser without breaking the layout.
  • Animation is switched off automatically if your system asks for reduced motion.
  • Touch targets are at least 44 by 44 pixels and form fields are at least 16 pixels, so mobile browsers do not zoom on focus.
  • Headings run in order, images carry alternative text, and every page has a unique title.
  • There are no time limits, no automatic redirects, and no pop-up windows.

Known limitations

  • The fullscreen control uses your browser's fullscreen feature where it exists. Where it does not, the same button expands the content to fill the window instead, which behaves slightly differently.
  • The list of other Clandrix sites in the information panel is supplied by a shared script. If it fails to load, the panel still shows the main links.
  • The site has been checked by hand rather than audited by an outside firm. If something is unusable for you, that is a fault worth reporting.

Telling us about a problem

Email support@clandrix.com with the page, what you were trying to do, and the browser or assistive technology you were using. Accessibility faults are treated as bugs, not as feature requests.