Accessibility

Readable, keyboard-accessible, and predictable.

The public platform should be practical to navigate on desktop, laptop, tablet, and mobile screens without relying on heavy JavaScript or visual effects.

Keyboard support

Skip link, menu toggle, Escape-to-close behaviour, visible focus outlines, and link/button focus states are included.

Motion control

Reduced-motion preferences are respected so interface transitions do not become distracting or uncomfortable.

Contrast discipline

The dark/cyan interface uses high-contrast text and restrained accent usage for interactive states and section markers.

Static fallback

Content remains visible as plain HTML. JavaScript improves menu and copy helpers but does not own the information architecture.

Public standard

Accessibility is part of trust.

A public trust platform should be easy to read, easy to verify, and easy to navigate. The baseline favours simple markup, semantic headings, consistent links, and responsive layout rules.

Baseline checks

Front-end requirements

Skip link present Menu button labelled Focus-visible states defined Reduced motion supported Print style included Responsive menu retained Images have alt text Core pages work as static HTML