[webauthn] Advice on language to use? (#1708)

certainlyNotHeisenberg has just created a new issue for https://github.com/w3c/webauthn:

== Advice on language to use? ==
(This is not an issue but a question for the community. Just not sure where else to ask it. Apologies if this is the wrong place!)

I'm using WebAuthn and unsure what language to use so the user understands what's happening. I'd love anyone's input!

Specifically, I'm using the user's email address as the display name and defaulting to platform authenticators. So, there are two steps, where step 1 is "Enter Your Email". But I'm unsure what to call step 2.

I started with "Complete Biometric", but the platform authenticator won't always be a biometric — sometimes it'll be a passcode, or pattern, or PIN, etc. 

Then I tried the slightly more generic "Complete Biometric/Passcode Check", but that's a mouthful and still not totally accurate. 

Then I tried to see if I could customize the language based on the platform (e.g. "Complete Face ID" on a certain iPhone, "Complete Touch ID" on a different iPhone, etc.), but there are issues with that:
- There's no totally reliable way to know what platform the user is on.
- Even if you know the platform, there are often several options at the device level for what the platform authenticator would be. (E.g. on an RCA Q2 phone I have, I can set in phone settings the authenticator to be a passcode, PIN, or pattern.)

Another issue with the generic "biometric" term is that it can sound somewhat scary. The term itself doesn't distinguish between a platform biometric like Face ID, which users find familiar, and a whole new biometric like a third party facial recognition system, which users often find quite invasive.

I suppose "Complete Platform Authenticator Check" is the most accurate... but I doubt many users would have any clue what that means.

So I'm at a loss for what language to use! Any ideas would be very welcome. :)

Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1708 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 19 March 2022 17:45:45 UTC