True Measure / Contact journeys
Test your website’s inquiry path
Follow a permitted test from the contact action to actual receipt and responsibility.
Use paper or your own notes for answers and checklist marks. No answers are collected or saved on this page.
Follow one inquiry all the way through
Choose a contact path on a website you own or have permission to test. Agree on a harmless test with the person receiving it. Use a clear test label and avoid real customer information, sensitive documents, purchases, or bookings.
Record what happened at each step. A visible confirmation, actual receipt, and staff follow-up are separate things to verify. This sheet is a manual test log, not a complete website or accessibility audit.
Website / page:
Test date and time / tester:
Phone or computer / browser:
Path: ☐ Call link ☐ Email link ☐ Contact form ☐ Other:
Test label / agreed recipient:
1. Check the route to contact
For each row, record worked, problem, not tested, or not applicable, with a short observation.
| Check | Result and what you observed |
|---|---|
| Can you find the contact action on the chosen page? | |
| Is the action readable and usable on your phone? | |
| Does the link open the expected number, address, or form? | |
| Is it clear what information is needed? | |
| Using only the keyboard, can you reach and activate the contact controls, see where focus is, and complete or correct the form if present? |
For a call or email link, check the displayed destination before proceeding. Opening a dialer or email application is not the same as reaching the business.
2. Check a form, if this path has one
- ☐ Required fields are understandable before submission.
- ☐ A deliberately missing required value produces a useful message.
- ☐ The message explains what needs correcting.
- ☐ After correcting it, you can continue without an unexplained dead end.
- ☐ The agreed test submission produces an understandable result.
Exact error or confirmation wording:
Anything lost, confusing, or impossible to complete:
3. Verify receipt and responsibility
| Evidence | Result |
|---|---|
| Did the agreed destination actually receive the test? | |
| Who checked, and at what time? | |
| Were the necessary test details readable and complete? | |
| Who owns the next response? | |
| Does that person know the response expectation shown on the site? |
Do not attach customer messages or inbox screenshots containing private information. A test label, result, and time are enough for this log.
Fictional example: The page displayed “Thank you,” but the agreed inbox did not contain the test when checked. Record “confirmation observed; receipt not verified.” Ask the provider to investigate rather than marking the whole path successful.
Read the result
Describe the first point where the result differs from what you expected. If the path did not complete, record that plainly; one failure does not by itself explain the technical cause. After a change, repeat the same test and keep both results.
Problem / person responsible / planned correction:
Retest date / result / remaining unknown:
Source note
The W3C Forms Tutorial recommends clear feedback for form outcomes and understandable error-correction instructions. The receipt and response checks above are our practical test method; the W3C guidance does not certify inbox delivery. W3C’s preliminary accessibility checks also explain why a few checks cannot establish comprehensive accessibility.