Web Forms: Now You See Them, Now You Don’t! by Jason Grigsby

  1. Something you know (e.g. a password).
  2. Something you have (e.g. a security key).
  3. Something you are (e.g. biometric information).
  1. Start by reducing the number of form fields.
  2. Use the correct HTML to support autofill. Support password managers and password-pasting. At least don’t break that behaviour.
  3. Provide alternate ways of logging in. Federated login or the Credentials API.
  4. Test autofill and other form features.
  5. Look for opportunities to replace forms entirely with biometrics.

--

--

--

A web developer and author living and working in Brighton, England. Everything I post on Medium is a copy — the originals are on my own website, adactio.com

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Belacam Update: New Anti-Spam system

What happens when you type https://www.google.com in your browser and press Enter

{UPDATE} 火爆摩托车 - 真实赛车游戏之摩托飞车 Hack Free Resources Generator

Cybersecurity in 2019: 5 Questions Comms Leaders Should Ask Now

User Account Takeover Using Vulnerable Password Reset Features

You should stop relying on free VPNs because they are not private and slow

Hook Line and Sinker : Learning to Phish

Constellation Network $DAG

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jeremy Keith

Jeremy Keith

A web developer and author living and working in Brighton, England. Everything I post on Medium is a copy — the originals are on my own website, adactio.com

More from Medium

5 Reasons Why Candidate Onboarding is a Crucial Step

Tackling toxicity with anonymous surveys

Illustrated cartoon of person selecting happy face rating , 4 stars, on a tablet

Talk the Walk: The Walking Dead Universe became a Google Voice Action

VTEX — A Force To Reckon With