Accessibility
Text contrast ≥ 4.5:1, full keyboard navigation, labels on all fields, visible focus, reduced-motion support.
khairiq.online
Project stages, the artefacts each stage produces and the measurable quality criteria we agree with clients.
Durations below are planning ranges, not promises. We fix exact timings after the mapping stage.
| Stage | Duration | Artefacts | Done when |
|---|---|---|---|
| Conversation & brief | 1–2 meetings | 1–2 page brief Stakeholder list | Brief approved in writing |
| Research & map | 1–3 weeks | Journey map Prioritised backlog Risk register | Every journey has an owner and acceptance criterion |
| Prototype | 1–3 weeks | Clickable prototype Test notes from 3–5 people | Key tasks completed without prompting |
| Iterative build | 2-week sprints | Demo every sprint Code in your repository Automated tests | Lighthouse accessibility ≥ 90; zero critical bugs |
| Launch & handover | 1–2 weeks | Publishing or deployment Documentation Knowledge handover session | Your team can deploy using the guide |
Text contrast ≥ 4.5:1, full keyboard navigation, labels on all fields, visible focus, reduced-motion support.
Budget: LCP < 2.5 s on a mid-range phone, first-screen JS weight agreed up front.
Error messages explain what happened and what to do next. No unexplained codes.
Collect the minimum, record where data is stored and for how long.