Skip to content
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

[Redesign] Restore Password Flow Checklist #1151

Open
58 tasks done
Lahernyi opened this issue Feb 19, 2025 · 0 comments
Open
58 tasks done

[Redesign] Restore Password Flow Checklist #1151

Lahernyi opened this issue Feb 19, 2025 · 0 comments

Comments

@Lahernyi
Copy link
Collaborator

Lahernyi commented Feb 19, 2025

Date Time
02-19-2025 20:34

UI Redesign Testing Checklist

1. Password Reset Page (Initial Form)

  • The page displays a heading indicating "Restore Password."
  • A single input field is available for entering a new password, with a requirement note indicating. Password validation (as implemented).
  • A second input field is present to confirm the new password.
  • A "Save Password" button is clearly displayed, with appropriate styling to indicate interactivity.

2. Error Messaging for Password Fields

  • If the "New Password" and "Confirm New Password" fields do not match, an error message is displayed below the confirmation field stating: "Паролі не співпадають. Будь ласка, введіть однакові паролі в обидва поля."
  • If the password does not meet the specified requirements, an error message appears below the "New Password" field: "Пароль не відповідає вимогам"
  • Both error messages should be styled in red to draw attention and enhance accessibility.

3. Confirmation Message After Successful Reset

  • Upon successfully saving the new password, a confirmation page appears.
  • The message displayed reads, "Ваш новий пароль успішно збережено."
  • A button is provided with the label "Return to Login", which redirects the user back to the login page.

4. Responsive Design

  • The Restore Password Flow is optimized for desktop, tab and mobile views, ensuring the layout, input fields, and buttons are appropriately scaled and accessible on all devices.

5. Security Considerations

  • Password fields have an eye icon for toggling password visibility, allowing users to review their entries.

6. Footer Consistency

  • The footer includes company contact information, links to privacy policies, and a consistent style across all pages of the restore password flow, maintaining a cohesive brand experience.

7. General UI Layout

  • All elements are aligned as per the design specifications.
  • Spacing and padding between elements are consistent across the UI.
  • No elements are overlapping or cut off on any screen size.
  • Text, images, and icons render correctly and are not distorted.
  • The UI looks visually similar to the mockups in terms of colors, fonts, and sizes.

8. Responsiveness

  • Layout adjusts correctly for various screen sizes (desktop, tablet, mobile).
  • The UI adapts seamlessly when switching between landscape and portrait modes.
  • No horizontal or unnecessary vertical scrolling is needed on any screen size.
  • Important content is prioritized and remains visible on smaller screens.

9. Cross-Browser Compatibility

  • UI renders correctly in major browsers (Chrome, Firefox, Safari, Edge).
  • Fonts, colors, and images appear consistently across browsers.
  • Interactive elements (buttons, dropdowns, etc.) work as expected on all browsers.
  • CSS and animations are consistent across different browsers and versions.

10. Accessibility

  • Color contrast meets WCAG standards (AA level or higher).
  • All interactive elements are accessible via keyboard, with a visible focus state.
  • ARIA labels and roles are correctly applied to screen-reader elements.
  • Form fields have associated labels, error messages, and instructions where needed.
  • Screen readers can correctly interpret and navigate the redesigned interface.

11. Visual Consistency

  • All colors, fonts, and styles match the design specifications.
  • Hover, active, and disabled states for buttons and links are visually distinct.
  • Icons and images are high quality and scaled correctly.
  • Text truncation or overflow issues do not occur.
  • Consistent use of shadows, borders, and other UI styling elements.

12. Functionality

  • Buttons, links, and other clickable elements are functional and lead to the correct pages or actions.
  • All forms work as expected, including validation for required fields and error messages.
  • Dropdowns, checkboxes, and radio buttons are selectable and reflect the chosen options.
  • Modal dialogs open and close correctly, and focus remains within the modal while open.
  • Pagination (if applicable) works as expected and leads to the correct content.

13. User Feedback and Notifications

  • Success messages appear for completed actions (e.g., form submissions).
  • Error messages display when required fields are left empty or incorrect data is entered.
  • Warning or info messages are shown where applicable and are easy to understand.
  • Toasts, alerts, or modal messages do not overlap and are easily dismissible.

14. Forms and Input Validation

  • Placeholder text is clear and present in all input fields where needed.
  • Field validations work correctly, providing immediate feedback for errors.
  • Required fields are clearly marked.
  • Form submission buttons are disabled until all mandatory fields are correctly filled.
  • Error messages for invalid input are clear, visible, and context-appropriate.

15. Images and Icons

  • Images load correctly, with no broken links or placeholders.
  • Icons appear sharp and clear on all screen sizes.
  • Alt text is provided for all images, where applicable.
  • Logos and brand-related images are high quality and positioned correctly.

16. Interactive Elements and Hover States

  • Buttons and links change state (hover, active, focused) as per the design.
  • Interactive elements like accordions, tabs, and sliders function as expected.
  • Tooltips and pop-ups display correctly on hover or click.
  • No unintended hover or focus states appear on non-interactive elements.

User story links E.g.: "User story #864 "

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants