What journeys are in CheckFox and what they enable.
Cette documentation est disponible en anglais uniquement.
What a journey is
A journey is an ordered sequence of samples representing a user task across multiple pages. Example: "Sign up and complete first purchase" might be 5 samples in order: homepage, signup, email confirmation, product page, checkout.
Why journeys matter
Page-by-page audits can miss accessibility failures that only surface across pages. A focus management bug between two pages, a session-loss issue on form submission, or a navigation pattern that breaks under specific user flows are not caught by evaluating each page in isolation. See methodology / journey mapping for the full case.
Journey fields
- Name
- Description (the user goal)
- Ordered list of samples
- Notes per step (free text)
What you do with a journey
- Evaluate criteria across the journey, not just per sample.
- Document journey-specific findings (e.g., "focus is lost after form submission").
- Reference the journey in the report.
Plan availability
Journey mapping is available on Pro and Enterprise plans.
<!-- needs review: confirm plan gating -->Where it lives in the UI
- Audit page > Journeys tab.
Related
- samples — samples are the building blocks.
- methodology / journey mapping — why and when to map.
- procedures / map a journey — how to map one.