Working standards

A quality bar teams can discuss.

Our baseline combines semantic implementation, clear content, resilient interaction and evidence from people using the service.

Content

Purpose before detail

Every page should explain what it is, who it is for and what can happen next. Headings describe the content that follows. Links name their destination.

Structure

Semantics match meaning

Use native headings, landmarks, lists, links, buttons and form controls according to their purpose. Visual appearance must not be the only source of structure.

Obvious default: choose the native HTML element before inventing a custom component.

Interaction

Works without a pointer

All actions remain available by keyboard. Focus is visible, order is logical and controls do not trap navigation. Layouts remain usable when text or page zoom increases.

Testing

Use several kinds of evidence

Automated checks catch a valuable subset of defects. Add keyboard review, screen-reader sampling, zoom and reflow checks, content review and task-based research with relevant users.

Scope and compliance

These educational standards are not a certification and do not establish compliance with a specific law or procurement requirement. Teams should identify the formal obligations that apply to their service.