Since users do not have to remember passwords that the browser stores for them, they are able to choose stronger passwords than they would otherwise.įor this reason, many modern browsers do not support autocomplete="off" for login fields:
MOZILLA FIREFOX LOGIN PASSWORD
When the user visits the site again, the browser autofills the login fields with the stored values.Īdditionally, the browser enables the user to choose a master password that the browser will use to encrypt stored login details.Įven without a master password, in-browser password management is generally seen as a net gain for security. Modern browsers implement integrated password management: when the user enters a username and password for a site, the browser offers to remember it for the user. This means that the criterion can be passed (by adding the relevant autocomplete attributes to individual form fields) even when autocompletion for the form itself has been turned off. Note that the WCAG 2.1 Success Criterion 1.3.5: Identify Input Purpose does not require that autocomplete/autofill actually work - merely that form fields that relate to specific personal user information are programmatically identified. As website author, you might prefer that the browser not remember the values for such fields, even if the browser's autocomplete feature is enabled. However, some data submitted in forms either are not useful in the future (for example, a one-time pin) or contain sensitive information (for example, a unique government identifier or credit card security code).
These features are usually enabled by default, but they can be a privacy concern for users, so browsers can let users disable them. This enables the browser to offer autocompletion (that is, suggest possible completions for fields that the user has started typing in) or autofill (that is, pre-populate certain fields upon load). This article explains how a website can disable autocomplete for form fields.īy default, browsers remember information that the user submits through fields on websites.
0 kommentar(er)
