Accessibility statement

CASRAI is an editorial-publishing site for an audience that includes researchers, librarians, publishers’ production staff, and policy workers — many of whom use assistive technologies as a matter of course. We treat accessibility as part of editorial quality, not as a downstream compliance task. The substantive content is also licensed CC-BY 4.0 and exposed in machine-readable formats (markdown for LLMs, GraphQL, JSON-LD, RDF Turtle), so reuse by alternative renderers and assistive workflows is a first-class consumer of the site, not an afterthought.

This page describes the current state. It is a living document: when a gap is found we add it to the known-issues list with a target window, and remove it when shipped. The page is reviewed at every release point (twice per year) and after any third-party audit.

The list below is implemented site-wide, on every page rendered by our editorial application. Components in src/components all go through the same set of checks, so the list applies to dictionary entries, editorial pieces, CRediT pages, and tooling alike.

• “Skip to main content” link as the first focusable element on every page.
• Single <h1> per page; no skipped heading levels in the document outline.
• Visible keyboard focus indicators with at least 3:1 contrast against any background they can land on.
• Form inputs have explicit <label> elements; no relying on placeholder text as the only label.
• All meaningful images have alt text; decorative images use alt="" and role="presentation".
• Colour-contrast tested across the parchment palette: 4.5:1 for normal text, 3:1 for large text and meaningful graphical objects.
• Unique, descriptive <title> per page; the title-trimming logic in our layout preserves uniqueness within the 50-character SERP budget.
• 200% page zoom usable without horizontal scrolling; reflowing tested in Chrome, Firefox, Safari, and Edge.
• Respects prefers-reduced-motion: the CRediT wheel, the adoption timeline, the marquee carousel, and any other animated element stop moving or render a static equivalent.
• HTML lang attribute set per page (currently en-GB; per-translation language attributes ship once language-committee outputs are signed off — see /credit/translations).
• Interactive elements meet the 24×24 CSS-pixel target-size minimum from WCAG 2.2 AA where they can; we’re measuring the few exceptions ahead of formal 2.2 adoption.
• ARIA used sparingly and only where native HTML semantics fall short; landmark roles (main, nav, aside) on the layout primitives.

Accessibility feedback goes to [email protected]. We acknowledge within 5 working days. We aim to fix critical issues — anything blocking core task completion for a class of users — within 14 days; cosmetic or low-impact issues land in the next sprint.

When reporting, please include (where you can) the URL of the page concerned, the assistive technology and version (e.g., NVDA 2024.4 on Firefox 140 on Windows 11; or VoiceOver on Safari 18 on macOS 15), what you heard or saw, and what you expected instead. We don’t need a perfect bug report — even “the dictionary domain page doesn’t make sense with my screen reader” gives us enough to start reproducing.

If accessibility is blocking you from completing a task you need to complete today, say so in the subject line (“URGENT — blocking”) and we’ll prioritise. For broader site contact see /contact.