Verify the phone number, link and receiver
Show a readable number, an understandable destination and a usable mobile calling action, with a truthful alternative outside supported hours. Test keyboard reachability and the prepared dialer separately from receiver confirmation. A tap is evidence of interface use; it is not an answered call or a qualified enquiry.
Worked example — illustrative data.
| Check | Expected behavior | Evidence |
|---|---|---|
| Readable number and label | Customer knows which shop/team receives it | Approved business contact |
| Tap phone link | Device opens intended calling action | Displayed destination compared with number |
| Keyboard access | Link is reachable with visible focus | Navigation observation |
| Outside calling hours | Verified hours and supported alternative | Owner-confirmed contact state |
| Wrong-device case | Number can still be copied or read | Desktop review |
Confirm the canonical phone destination with the business owner before implementing the link. Include the appropriate dialing format and test on an actual phone without making an unauthorized live call. A dialer opening is one check; reaching the responsible team requires a separately approved end-to-end test. Review page context so sales, pickup and existing-order questions do not all appear to reach a different team.
Label the number by the action it supports
Put the intended receiver and relevant calling hours beside the phone action. In the shop example, keep an existing-order contact separate from a new-stock enquiry if different teams answer them. Test the visible number and phone-link destination on the same device, then check the supported alternative outside calling hours. A tap only demonstrates an attempted contact action.
Decision: Accept the interface when the link, visible number and intended receiver agree. Keep answered-call and qualified-enquiry reporting separate from link taps.
A tracking number needs verified routing and fallback: A tracked phone number can differ from the canonical public number. The measurement owner must explain the routing and fallback rather than letting two conflicting numbers spread across pages.
Should the call button be the only way to find the number?
Keep the number readable as text as well as actionable where supported. A desktop visitor may need to copy it, and a mobile visitor may want to check which branch will answer before starting a call.
Continue with Guides for stores, software teams and local businesses, Website design for local businesses and Test a local business contact page.
For keyboard operation and visible focus, see the W3C WCAG quick reference.