When sign-in requires reading and retyping codes, it can create a cognitive-function barrier. Passkeys offer a passwordless alternative that avoids code transcription. section 7.3.2 section 7.6
When a passkey is created, the web application receives a public key while the private key stays on the user’s authenticator. At sign-in, the application sends a cryptographic challenge; the user authorizes it by unlocking the passkey, and the authenticator returns a signature the application verifies. Biometric data is not disclosed to the website. section 7.3.2
Authenticator options
A passkey may be unlocked using an authenticator built into a laptop, such as Windows Hello, an Apple device using Face ID, a mobile phone, or a hardware security key such as YubiKey or Google Titan Security Key. Do not make biometrics the only authentication option. section 7.3.2 section 7.3.2
Consider access when a user’s authenticator is unavailable: some passkeys synchronize across devices, while others are tied to one device and may become inaccessible if it is lost or unavailable. section 7.3.2

