Have you ever tried to enter your email address on a mobile form and the keyboard showed numbers instead of letters? Or worse, you had to hunt for the @ symbol buried in a secondary keyboard menu?

The problem is the code, not the keyboard

Mobile devices are smart enough to show the right keyboard for different types of input. But they need developers to tell them what kind of information belongs in each field. Without that signal, your phone defaults to a standard keyboard that makes every input harder than it needs to be.

What typically goes wrong

  • Email fields that don’t show the email keyboard (the one with the @ symbol front and center)
  • Phone number or ZIP code fields that bring up the full keyboard instead of the numeric keypad
  • Date fields that force manual typing instead of showing a date picker

The fixes are straightforward

Start by using the correct HTML input type for each field. Email fields should use type="email", phone numbers should use type="tel", and so on. For fields that need only numbers (like ZIP codes), add inputmode="numeric" to trigger the number pad.

Test your forms on mobile

Pull out your phone and fill out your contact form, or go through your checkout process. Pay attention to which keyboard appears for each field.

Getting the right keyboard to appear is a quick fix that removes friction for mobile users.

Don’t Miss Out

Get practical accessibility tips in your inbox every week.

Matt Litzinger headshot

Matt Litzinger

Matt is a web developer who builds tools that help organizations better engage with customers and improve website accessibility.