-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorporate improvements for user authentication forms #582
Comments
For the first point, here is the current state (and in brackets what I propose): Login
Registration
Forgotten passwordAsk email scren
New password screen
Identity
Is it any good? I'm not sure which is preferable between "username" and "email". |
Points 2, 3, 4, 5, 6, 7 and 9 seem good. Point 8 ("Mark invalid fields for screen-readers") is not good. I don't know about points 10 and 11. I haven't checked in detail, but here's what emerges from a (very) quick analysis. |
Hello @yannicka
I think it would be email, and from what I remember this was the main improvement I wanted to include to forms in Hummingbird.
10 - I think we're good. 11 - this is worth checking, every single action that takes time and is being sent via AJAX should indicate that something is going on, I think it works better in Hummingbird but I haven't checked everything |
So:
|
We can also go a little further with the other autocomplete values for the first name, surname, address, postcode, telephone number, etc. (on PrestaShop code) |
More details:
https://evilmartians.com/chronicles/html-best-practices-for-login-and-signup-forms
Details to be specified.
The text was updated successfully, but these errors were encountered: