Delivery standards
The form we hold every release to
These are the standards we apply to every project. They describe what we do, not certificates we claim. If we ever fall short of one, we will tell you and explain what we are doing about it.
- Done means donedefinition
A feature is finished when it is built, reviewed by a second developer, covered by tests where sensible, checked for accessibility, demonstrated to you and documented. Anything less is reported as in progress.
- Testinglayers
Automated unit and integration tests run on every change. Critical journeys get end-to-end tests. Manual testing covers an agreed list of real devices and browsers, written down before testing starts.
- AccessibilityWCAG 2.2 AA target
We design and test against WCAG 2.2 level AA: keyboard access, focus visibility, contrast, labelled controls, text resizing and reduced-motion preferences. Known gaps are listed in the handover.
- Securityby habit
Secrets kept out of source code, least-privilege access, dependencies scanned, personal data minimised, and access removed for anyone who leaves the project.
- Reportingevery cycle
A short written summary at the end of each cycle: what shipped, what slipped and why, risks we can see coming, and decisions we need from you.
- Handoverno lock-in
Code, designs, credentials and documentation transferred to accounts you control. A new team should be able to build and release without calling us.
Interactive
Is your project ready to ship?
A self-check you can run on any project, ours or anyone else's.