Menu
  • UX Trending
  • UX PODCASTS
    • DESIGN UNTANGLED
    • UX CAKE
  • UX Reading Room
  • UX Portfolio Building
  • UX JOBS
    • Atlanta
    • Dallas
    • Los Angeles
UXShareLab… everything you need to know about UX and more…
for the user experience design community

Search

Browse: Home   /   Should I manually hyperlink phone numbers using "tel:" on my websites?

Should I manually hyperlink phone numbers using "tel:" on my websites?

by UXStackExchange on May 8, 2012 in Devices, E-Commerce, Forms, General, Information Architecture, Interaction Design, Interfaces, JavaScript, LA UX Jobs, Marketing, Material Design, Mobile, Personas, Product Strategy, Prototyping, Resources, Responsive Web Design, Stakeholder interviews, Testing, UI, Usability, User Experience, User Interaction, User Research, User testing, UX Design, UX Rockstars, UX Toolbox, Visual Design

In code, you have the ability to make a phone number on a website into a link by prepending the phone number in the href with a "tel:"

So, for example, you can create a link to 800-867-5309 with the following:

<a href="tel:+18008675309">800-867-5309</a>

Some phones will automatically turn any properly formatted phone number into a link that, when clicked, will prompt you to see if you'd like to dial said number (iPhones for example).

Does it make sense to do add these links manually so the phone numbers show up linked on desktops?

On a desktop computer, when you click on one of these links, the computer will try to open some sort of default communication program.

If you have not set a default communication program, this might be a little jarring as it might open a completely unfamiliar program, which I would think falls under the "unexpected results" realm.

Is there any best practice for this sort of thing?

Should phone number links, perhaps, be formatted differently than other links?

Tags: ux stack

Sign Up for the latest in UX News...

Enter your email address to subscribe to UXShareLab and receive notifications of new posts by email.

Join 834 other subscribers

Related Posts

When does a contact list get too long for a review?
When does a contact list get too long for a review?
Editor for teachers to create exam, exercises, and questions
Editor for teachers to create exam, exercises, and questions
How should I handle the Esc key in a "Press any key" screen?
How should I handle the Esc key in a "Press any key" screen?
Is there a name for "mirrored" layout?
Is there a name for "mirrored" layout?

Should I manually hyperlink phone numbers using "tel:" on my websites?

by UXStackExchange on May 8, 2012 in Devices, E-Commerce, Forms, General, Information Architecture, Interaction Design, Interfaces, JavaScript, LA UX Jobs, Marketing, Material Design, Mobile, Personas, Product Strategy, Prototyping, Resources, Responsive Web Design, Stakeholder interviews, Testing, UI, Usability, User Experience, User Interaction, User Research, User testing, UX Design, UX Rockstars, UX Toolbox, Visual Design

In code, you have the ability to make a phone number on a website into a link by prepending the phone number in the href with a "tel:"

So, for example, you can create a link to 800-867-5309 with the following:

<a href="tel:+18008675309">800-867-5309</a>

Some phones will automatically turn any properly formatted phone number into a link that, when clicked, will prompt you to see if you'd like to dial said number (iPhones for example).

Does it make sense to do add these links manually so the phone numbers show up linked on desktops?

On a desktop computer, when you click on one of these links, the computer will try to open some sort of default communication program.

If you have not set a default communication program, this might be a little jarring as it might open a completely unfamiliar program, which I would think falls under the "unexpected results" realm.

Is there any best practice for this sort of thing?

Should phone number links, perhaps, be formatted differently than other links?

Tags: ux stack

Related Posts

Weekly News for Designers № 613
Weekly News for Designers № 613
Weekly News for Designers № 597
Weekly News for Designers № 597
WCAG 3.0 structure and assessment criteria benefits in current practice
WCAG 3.0 structure and assessment criteria benefits in current practice
Weekly News for Designers № 646
Weekly News for Designers № 646
← Are there numbers and letters to avoid for activation codes via SMS?
Indeterminate state for toggle buttons? →

Topics

WordPress Gutenberg Universal Design & Accessibility User Experience User Research Usability UX Jobs Atlanta web-app UX Jobs in Atlanta UI design User testing Web Design uxstackexchange Visual Design WordPress Plugins UX UX Jobs Dallas uxbooth UX Jobs Los Angeles wordpress user-behavior User Interaction UX Design UX Toolbox UI UX Rockstars

Feeds

UI UI design Universal Design & Accessibility Usability user-behavior User Experience User Interaction User Research User testing UX uxbooth UX Design UX Jobs Atlanta UX Jobs Dallas UX Jobs in Atlanta UX Jobs Los Angeles UX Rockstars uxstackexchange UX Toolbox Visual Design web-app Web Design wordpress WordPress Gutenberg WordPress Plugins

<span>recent posts</span>

  • UX in 2018: The human element

    • Anywhere
  • Three Takeaways from the Hawai’i Missile False Alarm

    • Anywhere
  • UX in 2018: Content

    • Anywhere
  • UX in 2018: Design, Development, and Accessibility

    • Anywhere
  • The Power and Danger of Persuasive Design

    • Anywhere

connect to uxsharelab

Enter your email address to subscribe to receive notifications of new posts by email.

UXShareLab. Copyright © 2018. All rights reserved.

  • Contact UXShareLab
  • UXShareLab Community
  • UX PROCESS
  • Recommended Reading
  • UX StackExchange