Map a user journey across phases and touchpoints, and link it to your audits.

Goal

Map one user experience across the touchpoints of the service, and connect it to the audits that cover them.

The workspace has Journeys: included from Pro, an add-on on Free and Starter.
You can state the user goal in one sentence.
Ideally the audits covering the main touchpoints already exist, so they can be linked.

Go to Operations > Journeys and click Create new journey.
Name it after the user goal ("Sign up and complete a first purchase") and describe that goal in the description.
Add the phases, in order, from first contact to after the task is done.
In each phase, add the touchpoints the user actually meets: pages, emails, PDFs, an app screen, a call centre. Mark a touchpoint not auditable when it is outside what CheckFox can assess, rather than leaving it out.
Link an audit to each auditable touchpoint. That is what turns the map into accessibility coverage.
Set the emotional rating per phase, from very frustrated to delighted.
Record the opportunities and pain points, with a severity, and attach them to the audit that evidences them where one exists.
If several journeys share a set of phases, map that set once and link it into the others as a read-only block.

CheckFox ships a template journey. Duplicating it is often faster than starting empty.

The journey card shows its phase and touchpoint counts, and an accessibility coverage percentage rather than "not started".
Every auditable touchpoint links to an audit.
The public link, if you generated one, opens for someone who is not signed in.

Mapping pages instead of experience. A journey that never leaves the website is usually a sample list. The emails, the PDFs and the support call are the point.
Too many journeys. More than 5 usually means they are too granular. Combine them.
Omitting the goal. Without a stated goal, the journey is an ordered list and nobody can tell what counts as success.
Deleting a touchpoint to remove an audit. Deleting unlinks the audit but never deletes it, which is what you want; deleting the phase removes its touchpoints too.