# Accessibility journey worksheet

Blank working document. Replace placeholders with your own evidence; an empty field is unknown, not a passing result.

Owner: [fill in]
Source revision: [fill in]
Environment: [fill in]
Evidence date: [fill in]

## Environment

Journey: ___
URL/revision: ___
Browser/viewport: ___
Input method/assistive technology: ___
Guideline URL/hash/date: ___

## Interaction expectations

Start state: ___
Keyboard sequence: ___
Expected focus/announcement: ___
Error recovery: ___

## Observed issues

| Step | Expected | Observed | Evidence | Source location |
| --- | --- | --- | --- | --- |
| ___ | ___ | not run | ___ | ___ |

## Retest scope

Fix revision: ___
Retest result: not run
Untested technology/states: ___
Task impact and owner: ___

## Boundaries

- A browser server can submit forms and change remote state. Use test accounts and fixtures appropriate to the journey.

- Static guideline checks, DOM inspection and an automated scan do not establish full accessibility conformance. The guideline file is mutable and must be captured for reproducibility.

Workflow: https://undominated.ai/workflows/#audit-an-accessible-user-journey

Original worksheet: MIT. Linked resources retain their own licences and setup requirements.