Keep the login page identifiable
Keep login information central; Promotional content should not push the form out of the viewport.
Login Website
Let people returning to the website access your account in the right context.
Checklist contents
Review progress
01
Content and expectations
Compare information and presentation in context of use.
02
Navigation and experience
Try the operation, change the status and continue working.
03
Complete the experience
Check for details that are easy to miss when putting the design into use.
04
Branches need to be checked
Try specific scenarios when starting, changing, and completing tasks.
Progress is saved automatically in this browser.
GUIDANCE
How to review
EXAMPLES
Usage examples
Keep the login page identifiable
The login page places the form before the new feature introduction.
Variants and use cases
Centralized login form
Keep login information and recovery routes in an easy-to-scan area.
Try using just your keyboard and password manager; Don't force the user to re-enter email after an error.
Example The email, password, and Forgot password labels are on the same form.
Login with provider selection
Distinguish logging in with account information from third-party methods.
Try canceling the provider or missing permissions; Explain and return another way.
Example The vendor button has a specific name, not just a logo.
Secondary information keeps the main task
Updates or comments can be introduced when it helps users, but do not obscure access.
Try narrow viewport and text zoom; the introduction must give way to the form.
Example New feature descriptions are next to the desktop form, collapsed on mobile.