Standards
What good looks like, in plain words.
These are the standards we work to on every portal, how we check them, and where they stop.

Standard one
Words
Every label, status, error and email is written for a new user. We test key wording with people unfamiliar with your internal language, and keep a glossary so terms stay consistent.
Standard two
Accessibility
Keyboard operation, visible focus, screen-reader labels, sufficient contrast, readable type, and error messages that explain how to fix the problem. We check against WCAG 2.2 AA success criteria that can be tested without a specialist audit, and recommend an independent audit where your obligations require one.
Standard three
Honest states
A portal must never show something as done that is not. We design states carefully: received, in progress, waiting for you, complete. Where information is synchronised rather than live, we say when it was last updated.
Standard four
Personal data
We collect only what the service needs, restrict access by role, log significant actions and agree retention with you. We are not a certification body; we work with your data protection lead.
Standard five
Maintainability
Your administrators manage content and users. Code lives in your repository; accounts are yours; documentation explains how things fit together.