Can inaccessible contact cost enquiries?
Yes. If someone cannot read, reach or operate the phone number or form, they cannot enquire — even when the page is indexed and the business is nearby.
Typical pattern: a phone saved as an image, a form that ignores the keyboard, low-contrast footer text, or a tap target smaller than a thumb. This is an access and conversion job. It is not a claim that WCAG scores rank you in Maps.
Is this the same as broken click-to-call?
Overlapping, but not the same. A malformed tel: href fails for everyone who taps. An inaccessible number can fail for people using a screen reader, keyboard or low vision even when the href is valid.
Fix the URI on why click-to-call is not working on the local website. Stay here when the markup works for a typical tap and still excludes people.
Is this the site accessibility statement?
No. Otepsphere’s own accessibility page is a policy statement for this site, not a diagnostic for your location URLs.
Use Otepsphere’s accessibility statement if you need this website’s contact route. Your shop’s contact block is this guide.
Image
Is the number only a picture? WCAG expects text alternatives. A phone as an image can hide the number from a screen reader.Keyboard
Can you reach submit without a mouse? A form that traps focus or ignores Enter will lose enquiries.Contrast
Can people read the number and labels? Low-contrast footer text is a common way a local page hides contact.Sibling
A malformed tel link is a different job Use the click-to-call guide if the href is wrong, even when the text is accessible.Next
Do not treat this as a ranking factor The job is that more people can enquire. Search does not score WCAG as a rank lever.
Which access problems show up on local pages?
Images of phone numbers without a text alternative, forms that cannot be used with a keyboard, contrast that hides the number, and tap targets that are too small.
W3C’s WCAG 2.2 quick reference is the criteria set. Source: How to Meet WCAG (Quick Reference). Accessibility principles are summarised at Accessibility principles. Google’s helpful-content guidance still asks for pages people can use. Source: Creating helpful, reliable, people-first content. None of those documents treat a WCAG score as a local ranking factor.
Is this missing local proof on the page?
No. Local proof is whether the page shows you operate at that premises — NAP, photos, team — for customers and for retrieval.
Use why a location page lacks local proof for thin city templates. Stay here when contact exists but some people cannot use it.
Contact-access decision table
| What you see | What it usually means | Decision | What not to assume |
|---|---|---|---|
| Phone is a JPEG in the header | No text alternative or tel link | Publish the number as text in a tel link | That hiding the number from scrapers is safer |
| Tab never reaches submit | Keyboard trap or missing focus | Make every control reachable and operable | That only “real customers use a mouse” |
| Tap opens nothing for everyone | Malformed tel href | Use the click-to-call guide first | That this access page rewrites the URI |
| Page has no address or shop photos | Missing local proof | Use the local-proof guide | That contrast fixes premises facts |
What should I not do?
Action checklist
- Replace image-only numbers with text inside a tel link.
- Tab through the form to submit without a mouse.
- Check contrast on the number, hours and labels.
- Enlarge tap targets on the phone and book controls.
- If the href is wrong for everyone, switch to click-to-call.
- Do not treat WCAG as a local ranking factor.
When professional help makes sense
Help is useful when a theme hides contact in canvas or icon fonts. It is not a full legal accessibility audit, and it cannot promise rankings from a more usable number.
Sources and further reading
- W3C: How to Meet WCAG (Quick Reference)
- W3C WAI: Accessibility principles
- Google Search Central: Creating helpful, reliable, people-first content
Contact details still unusable for some customers?
Otepsphere can make the number and form operable — without treating accessibility as a ranking lever.
Contact OtepsphereWho writes this
This page is published by Otepsphere, a specialist Local SEO consultancy. A named founder biography, photograph and professional profiles will be added here only when they have been verified. Until then, treat Otepsphere as the responsible organisation rather than a fictional expert.