Accessibility

Our standard

We target WCAG 2.1 Level AA — the internationally recognised standard for web accessibility. This covers perceivability, operability, understandability, and robustness for a wide range of assistive technologies and disabilities.

What we've built in

Keyboard navigation

Every interactive element — links, buttons, form fields, menus — is reachable and operable by keyboard alone.
A skip to main content link appears as the first tab stop on every page, so keyboard users can bypass the navigation bar.
The mobile navigation menu traps focus while it's open and returns focus to the trigger button when closed.
The cookie preferences modal traps focus while open and returns focus to the button that opened it.
Navigation dropdowns open on hover and on keyboard focus, so they're accessible without a mouse.

Screen readers

All pages declare lang="en-GB" so screen readers use the correct pronunciation rules.
Decorative icons and SVGs are marked aria-hidden="true" so they're skipped.
Every form input has a visible or visually-hidden label.
Landmark regions (<header>, <main>, <nav>, <aside>, <footer>) are used throughout so screen reader users can jump between sections.
Navigation menus have descriptive aria-label attributes to distinguish "Main navigation", "Mobile navigation", and "Footer navigation".
Links that open in a new tab include a visually-hidden "(opens in new tab)" notice.
The "Copy link" button announces "Copied!" to screen readers via a live region when activated.
Breadcrumb navigation uses aria-label="Breadcrumb" and separator characters are hidden from the accessibility tree.
FAQ accordions use native <details>/<summary> elements, which are natively accessible across all screen readers.
Article table-of-contents navigation has aria-label="Jump to section" so it's distinguishable from the main nav.

Visual design

All text meets WCAG AA contrast ratios: body text achieves at least 7:1, muted text at least 5:1, and accent colour text at least 5.2:1 against its background.
Category tag colour pairs are chosen to meet 4.5:1 contrast between text and background.
Focus indicators are visible for keyboard users on all interactive elements: a 2px green outline appears on focus via :focus-visible, without affecting mouse users.
Font sizes use relative units (rem/em/clamp) so the site reflows correctly at up to 200% browser zoom.
Touch targets are at least 36×36 px to assist users with motor impairments.

Motion and contrast preferences

If your device or browser is set to reduce motion (e.g. via "Reduce Motion" in macOS/iOS accessibility settings, or the Windows "Reduce animations" setting), all CSS transitions and animations on this site are disabled automatically.
If your device is set to high contrast or "more contrast" mode, borders are strengthened and light background tints are darkened to improve visibility.
The site does not override OS-level high-contrast modes — if you use Windows High Contrast or similar, those styles take full effect here.

Structured data and page titles

Every page has a descriptive <title> and a <meta name="description">.
Article pages include JSON-LD structured data (Article, NewsArticle, FAQPage, BreadcrumbList) to help assistive technology and search engines understand the content hierarchy.

Known limitations

The admin panel (at /admin/) is not publicly accessible and has not been audited to WCAG AA — it is used only by the site editor.
Third-party ad scripts (when enabled) are outside our control. We ask advertising partners to provide accessible code, but cannot guarantee it.

Feedback and contact

If you encounter an accessibility barrier on this site — something you can't read, reach, or operate — please let us know. We take these reports seriously and aim to respond within 5 working days.