Hi @Vishwajith-Shettigar, it looks like some changes were requested on this pull request by @adhiamboperes. PTAL. Thanks!

I think that this is definitely a good approach.

The screenshots that you have shared don't seem to be from the accessibility scanner. Please refer to our wiki section on accessibility if you need help with that.

Here is accessability scanner screenshot.

Android version 10
When I scanned, I have got no suggestions, please guide me if something is wrong here.

Hey please tell is this issue android 12 specific, I haven't tried accessability Scanner with 12
Edit: Attached 12 also

Android 12
Accessability scanner screenshot

Here is accessability scanner screenshot.

Android version 10 When I scanned, I have got no suggestions, please guide me if something is wrong here.

Basically;

1. You need to be able to verify that you can reproduce the issue. You can do this by switching to a branch like develop, deploying your app on that branch, then running the accessibility scanner for this screen. You should see the warnings same as in the issue description. (Save the screenshot, because you need to add it it to the description of this PR)
2. Next, switch back to your branch(that contains your fix), and deploy the app, test it with the accessibility scanner. essentially, if your fix works, all the warnings should be gone(no suggestions). You will also add this screenshot to the PR description for before/after proof.

Your changes have led to some failing tests, here is information on how to find what is broken, so you can update the code or tests as appropriate.

Here is accessability scanner screenshot.
Android version 10 When I scanned, I have got no suggestions, please guide me if something is wrong here.

Basically;

1. You need to be able to verify that you can reproduce the issue. You can do this by switching to a branch like develop, deploying your app on that branch, then running the accessibility scanner for this screen. You should see the warnings same as in the issue description. (Save the screenshot, because you need to add it it to the description of this PR)
2. Next, switch back to your branch(that contains your fix), and deploy the app, test it with the accessibility scanner. essentially, if your fix works, all the warnings should be gone(no suggestions). You will also add this screenshot to the PR description for before/after proof.

Here is before fix

After fix

The screenshots look good. Thanks!

Hi @Vishwajith-Shettigar, once you are done making changes, please do the following:

• Go to the PR description and make sure you have done all the items on the Essential Checklist, and check them off
• Assign the PR to Ben Henning by mentioning him with "@(Ben Henning), PTAL".

Hi @Vishwajith-Shettigar, once you are done making changes, please do the following:

• Go to the PR description and make sure you have done all the items on the Essential Checklist, and check them off
• Assign the PR to Ben Henning by mentioning him with "@(Ben Henning), PTAL".

hey actually I'm not able to understand why my checks are failing, can you give some idea about this please, that would be very helpful. @BenHenning

Unassigning @Vishwajith-Shettigar since a re-review was requested. @Vishwajith-Shettigar, please make sure you have addressed all review comments. Thanks!

Can you guide me why some checks are failing please ?

I have left one nit comment - and for complete approval please update your PR description to include the following:

• An explanation of the changes that you have made
• Before(build using develop branch) and after screenshots(build app using your branch) of accessibility scanner showing that the warning is shown before your fix and gone after the fix. You can look at table formatting in markdown to organize your screenshots. Please see this for example.

I have made some changes PTAL, thank you.

I have made some changes PTAL, thank you.

Thanks. Do you know why the lightmode screenshot of the "after" fix is showing new suggestions?

I have made some changes PTAL, thank you.

Thanks. Do you know why the lightmode screenshot of the "after" fix is showing new suggestions?

no, I dont have any idea about that.

I have made some changes PTAL, thank you.

Thanks. Do you know why the lightmode screenshot of the "after" fix is showing new suggestions?

no, I dont have any idea about that.

Well, could you please share the suggestions?

I have made some changes PTAL, thank you.

Thanks. Do you know why the lightmode screenshot of the "after" fix is showing new suggestions?

no, I dont have any idea about that.

Well, could you please share the suggestions?

seems like its about background and foreground contrast ratio.

I switched to develop branch,now it shows same with light mode (api 31)

I switched to develop branch,now it shows same with light mode (api 31)

I checked this and the issue appears on the beta version as well. I don't think that should block this PR since the toolbar issue is fixed.

@Vishwajith-Shettigar, do you mind creating a bug report for the contrast issue?

@BenHenning, PTAL.

I switched to develop branch,now it shows same with light mode (api 31)

I checked this and the issue appears on the beta version as well. I don't think that should block this PR since the toolbar issue is fixed.

@Vishwajith-Shettigar, do you mind creating a bug report for the contrast issue?

@BenHenning, PTAL.

@adhiamboperes Sure, thank you.

Unassigning @Vishwajith-Shettigar since a re-review was requested. @Vishwajith-Shettigar, please make sure you have addressed all review comments. Thanks!

Unassigning @adhiamboperes since they have already approved the PR.

Merging this since a seperate issue #5142 has been created for the edit text contrasts.