Accessibility

Practical access features, readable colour choices, and ways to report a barrier.

Built for different ways of reading

The interface uses labelled native form controls, semantic headings and landmarks, keyboard-operable buttons and links, a skip link, visible focus styles, and expandable FAQ elements. Results use a status announcement when generated. Layouts reflow on narrow screens, and result tables have a labelled scrolling region when needed. There are no timed tasks, auto-playing animations, or colour-only error messages.

Use your browser’s zoom, text resizing, and print controls as needed. Reduced-motion and forced-colour preferences are respected. Essential information is not hidden behind hover-only controls. JavaScript is required for the tools; a no-script notice explains this.

Brand colours and high-contrast view

The site uses a white canvas (#FFFFFF), navy headings and body text (#102A43), and teal buttons and links (#006D77). Secondary text uses slate (#486176), with pale teal panels and light decorative rules. Navy text on white has approximately 14.6:1 contrast, and white text on teal has approximately 6.1:1 contrast. These primary text pairs exceed WCAG AA text-contrast thresholds. Decorative rules are not used alone to identify controls or convey essential information. This is not a claim of complete WCAG conformance.

Use High contrast in the header to switch text, backgrounds, borders, and controls to your browser’s system colours. This is an optional access mode, not an additional brand palette. Its appearance depends on your browser or operating-system theme, and the preference lasts only in the current loaded session. Your own forced-colour settings also take precedence.

Known limitations and feedback

Browser print dialogs, downloaded-file handling, email applications, external source websites, WordPress administration, and unrelated theme/plugin elements are outside this interface’s control. Not every assistive-technology combination has been tested. If a collection cannot be saved locally, export it instead.

To report a barrier, use Contact and include the page or tool, device/browser, assistive technology if relevant, the action you were attempting, and what happened. Do not send private collection contents unless they are essential to a reproducible example. A useful report helps the operator prioritize a specific fix; no response deadline is promised.