# Requirements and acceptance criteria

Keiss Media · Version 1.0 · 15 October 2026

The example is fictional. It demonstrates completion, not the outcome of an actual project.

## Deliverables and exclusions

A Russian-language promotional website with three routes. No accounts, payments or visitor editing of routes.

## User scenario

Someone with one free hour wants to choose a suitable walk and find its starting point.

## Behaviour and states

Selecting a duration shows matching routes. No matches produces an explanation and a reset control. An external map opens only on request.

## How to verify

Select 60 minutes: only routes of an hour or less remain. Complete the selection using a keyboard. Check no matches and reset. Save a test record and screenshots.

## Devices and quality

Layouts and checks for phone and desktop. Visible focus and labels that do not rely on colour. Loading targets and the browser list remain to be agreed.

## Review process

The delivery team checks the build, marketing reviews content and the client’s authorised reviewer approves it. A new language is a separate scope change.

## Sources and adaptation

- Agile delivery community, Government Digital Service: [Writing user stories](https://www.gov.uk/service-manual/agile-delivery/writing-user-stories). Open Government Licence v3.0.

Keiss Media’s existing worksheet was refined using GOV.UK guidance on user stories and acceptance criteria. Government-specific procedures and terminology were not carried over.

Contains public sector information licensed under the Open Government Licence v3.0.
https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/