Accessibility · readable by default

Moghrey Mie should be easy to scan, read and navigate.

Accessibility notes for the public website: mobile layout, keyboard-friendly links, restrained motion, readable source labels, known limits and how to report a problem.

Accessibility commitments

Practical design rules used across the static site.

Readable layout

Plain language and scan-friendly sections

Pages use headings, short cards, visible links and plain-English summaries so readers can scan the briefing without decoding raw document names.

Mobile support

Designed to work at phone widths

Website smoke tests capture mobile screenshots and check for horizontal overflow on public routes before changes are claimed.

Keyboard and focus

Links and buttons stay reachable

The static site relies on standard links and buttons. Interactive elements such as the subscribe popup include close controls and focus handling.

Motion restraint

No decorative motion dependency

The site avoids motion-heavy effects. Useful content and navigation should remain available without animation.

Source/link clarity

Links describe where they go

Reader routes, source links, FOI links, archive search and status pages are labelled to reduce mystery clicks.

Contrast and density

Visual review catches readability issues

Desktop and mobile screenshots are inspected for overlap, clipping, unreadable text, off-canvas content and severe density issues.

Known limits

These are the places where reader feedback is especially useful.

Found an accessibility problem?

Send the page URL, device/browser if known, and what was hard to use. Screenshots are helpful when safe to share.

Report accessibility issue

Latest issue for context: Rate of sexually transmitted infections after TT fell by a quarter last year.