Signal-android: Poor color contrast in information banner of "submit debug log" view.

[Meteor0id]

• [x] I have searched open and closed issues for duplicates
• [x] I am submitting a bug report for existing functionality that does not work as intended
• [x] I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
• [x] This isn't a feature request or a discussion topic

---

Bug description

Actual result: Words are difficult to read, especially when the phone dims during night time.
Expected result: Decent amount of contrast, even if the phone adjusts the color temperature during nightly hours.

Screenshots

[Meteor0id]

Do note that the text is quite readable here, but not so much on a small and dimmed phone screen.

[alan-signal]

Thanks, are you aware of the Accessibility Scanner app from Google?

It agrees on this item.

These kind of reports would be useful to help choose where to spend the effort first.

[Meteor0id]

These kind of reports would be useful

Why would you need such report? I just told you the contrast is insufficuent, didn't need this tool for it. Obviously the text should not be brown, or at least darker.

But glad it agrees with me.

Next time I see an issue like this I'll take that extra effort, didn't think it was important.

[greyson-signal]

Why would you need such report? I just told you the contrast is insufficuent, didn't need this tool for it. Obviously the text should not be brown, or at least darker.

This tool shows mathematically that there's too little contrast, as opposed to someone saying there is. It helps avoid personal bias. Also, please remember to be polite.

[Meteor0id]

I think it is impolite to question whether I am personally biased while I already provided a screenshot. Asking me to install and make use of a tool to double check something obvious just so there is mathematical proof, is a lot more effort on my side than it would be for you to look at the screenshot. By filing this ticket I already helped you "choose where to spend the first effort". If I file the ticket I think there is an issue.

But sure, if you prefer this method I will use that next time. It is an interesting tool and I am glad you pointed it out to me. I just question why it is important to include when a screenshot already shows the issue and it is visually obvious. A screenshot is already proof of the issue.

Excuse my accidental closing this issue, lets keep it open until it is fixed.

[greyson-signal]

We appreciate the report :) Alan was just suggesting a tool that can be used in the future. Instead of having to make comments like:

Do note that the text is quite readable here, but not so much on a small and dimmed phone screen

you can post the screenshot like Alan did, showing the bad contrast ratio. And to be clear, it was given as a suggestion, not a requirement.

Also wanted to clear up that when I said the tool helps avoid personal bias, I wasn't trying to disqualify your issue saying that you are biased, I was just answering your question of "Why would you need such report?" in the general case.

Thanks!

[Sgn-32]

There have been some changes in the "submit debug log"area prior to some versions.
Didn't find the exact version and the commit. But should be solved.

[Meteor0id]

I firgot to check if this issus had been marked solved. Let's not bother with finding the commit, it's solved.