<?xml version="1.0" encoding="utf-8"?>

The design consists of two screens: a Sign In page and a Sign Up page. Both screens follow a clean, minimalistic layout with a focus on clarity and usability. The design elements and choices ensure compliance with WCAG (Web Content Accessibility Guidelines) to provide an inclusive experience for all users, including those with disabilities.

1. Clear Labels and Instructions

2. Consistent Navigation:

• Both pages offer consistent navigation options (“Or continue with” for social logins, links to switch between Sign In and Sign Up) which helps users understand and predict where to find information.

3. Contrast and Readability:

• The text and input fields have high contrast against the white background, meeting WCAG contrast requirements (minimum contrast ratio of 4.5:1 for normal text).

• The blue “Sign In” and “Sign Up” buttons stand out clearly against the white background, ensuring they are easily identifiable.

4. Error Prevention and Assistance:

• The password field includes criteria (“Minimum 8 characters”) to help users create valid passwords, reducing the likelihood of errors.

• The “Forgot password?” link provides a way to recover from potential user errors.

5. Alternative Authentication Methods:

• Providing options to sign in or sign up with Google, Facebook, or Apple accounts supports users who might have difficulty typing or remembering passwords, thus enhancing accessibility.

6. Clear Call-to-Action:

• The primary actions (“Sign In” and “Sign Up”) are clearly distinguished by their size, color, and placement, ensuring they are the focal points of the screen.

Tools used

Figma

From brief

Topics

Share

Share your insights — leave a project review and help others grow their skills

Reviews

1 review


Great job! I really admire the way you've presented your work and explained the rationale behind it. The form is very clear and accessible; you've considered all the options to help users get back on track if they experience any difficulties.

My two cents from a UX Writer's perspective:

  • I'm not quite sure if the "Nickname" field is necessary here. If it is, it might benefit from a brief explanation: where it can be seen, whether it can be changed later, and any specific requirements.
  • I'm not certain if subtitles are needed here. They don't convey particularly important information, and the titles seem self-sufficient as they are.
  • Capitalization is a bit inconsistent: you use sentence case in titles and labels but switch to title case for buttons.

Awesome work—keep the momentum going!


10 Claps
Average 5.0 by 2 people
5 claps
4 claps
3 claps
2 claps
1 claps
<?xml version="1.0" encoding="utf-8"?>