Skip to content

fix: Secondary login page #6433

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

Merged
merged 1 commit into from
Nov 23, 2021
Merged

Conversation

parasharrajat
Copy link
Member

Details

This PR also update the behaviour of phone input for Add Login page.

  1. It will allow the user to enter any text into the input previously it was only accepting the + and digits.

I noticed that there are no frontend errors for phone input on this page. error is thrown after it is received from the backend.

Fixed Issues

$ #6414

Tests | QA Steps

  1. Navigate to NewDot and login
  2. Go to settings > profile
  3. Tap add phone number
  4. Input a phone number using any of symbols -, (, ) or spaces (e.g. +1 (222) 222 2222)

Tested On

  • Web
  • Mobile Web
  • Desktop
  • iOS
  • Android

Screenshots

Web | Mobile Web | Desktop

image

iOS

Android

@parasharrajat parasharrajat requested a review from a team as a code owner November 23, 2021 18:16
@MelvinBot MelvinBot requested review from chiragsalian and removed request for a team November 23, 2021 18:16
Copy link
Contributor

@chiragsalian chiragsalian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@chiragsalian
Copy link
Contributor

I briefly tested this. So i'm unable to perform this,

Input a phone number using any of symbols -, (, ) or spaces (e.g. +1 (222) 222 2222)

On web. Is that expected?

@parasharrajat
Copy link
Member Author

It should work on Web specially.

@chiragsalian
Copy link
Contributor

Yup, sorry my bad. I realized shortly after i was on an incorrect branch. Retested properly and it works great. Thanks rajat.

@chiragsalian chiragsalian merged commit a1eceeb into Expensify:main Nov 23, 2021
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@chiragsalian
Copy link
Contributor

Oh we should have placed the CP-staging label. Let me see if I can CP it to staging.

github-actions bot pushed a commit that referenced this pull request Nov 23, 2021
fix: Secondary login page
(cherry picked from commit a1eceeb)
@chiragsalian
Copy link
Contributor

Manually CP'd to staging to fix blocker.

@OSBotify
Copy link
Contributor

🚀 Cherry-picked to staging by @chiragsalian in version: 1.1.16-4 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

@OSBotify
Copy link
Contributor

🚀 Deployed to production by @roryabraham in version: 1.1.16-10 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by @chiragsalian in version: 1.1.16-11 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@ogumen
Copy link

ogumen commented Dec 1, 2021

The accessibility issues related to this PR:

  1. The initial focus upon opening Add phone number overlay is set to the Phone number text field instead of X (Close) button at the top of the overlay - failure of WCAG SC 2.4.3
    Add phone number_Initial focus is incorrect
  2. The grey placeholders and labels on white background fail minimum contrast requirements of 4.50:1 for small text. The font size is 11pt, wont weight 400. The grey (#7D8B8F) on white (#FFFFFF) has a color contrast ratio of 3.52:1 - failure of WCAG SC 1.4.3
    Add phone number grey text on white fails contrast requirements_1
    Add phone number grey text on white fails contrast requirements_2
  3. The grey buttons on white background fail minimum color contrast requirements of 3.00:1 against white background. The grey (#C6C9CA) on white (#FFFFFF) has a color contrast ratio of 1.66:1 - failure of WCAG SC 1.4.11
    Add phone number_Grey icons on white background fail contrast requirements
  4. The Add phone number visual heading is not implemented semantically as a heading - failure of WCAG SC 1.3.1
    Add phone number_The visual heading not implemented semantically as a heading
  5. The Back button is announced without label and role - failure of WCAG SC 4.1.2
Add.phone.number_Back.button.announced.unclearly.mp4
  1. The Send Validation button is announced without role - failure of WCAG SC 4.1.2
Add.phone.number_Send.validation.button.announced.with.no.role.mp4
  1. The blue visible focus outline for Send Validation button against green background fails minimum color contrast requirements of 3.00:1. The blue (#0185FF) against green (#03D47C) has a color contrast ratio of 1.84:1 - failure of WCAG SC 1.4.11
    Add phone number_Blue visual focus outline against green button fails contrast requirements

@OSBotify
Copy link
Contributor

OSBotify commented Dec 6, 2021

🚀 Deployed to production by @roryabraham in version: 1.1.17-7 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

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

Successfully merging this pull request may close these issues.

4 participants