Bug 382987 - Poor color contrast for unread messages
Summary: Poor color contrast for unread messages
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 5.5.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-01 08:14 UTC by Michael D
Modified: 2022-12-21 05:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael D 2017-08-01 08:14:16 UTC
The unread message foreground or font color with the default Breeze theme (a blue) is the color for "active", which is #3daee9. It is often over a gray background, i.e. #eff0f1. The contrast of this combination is a lowly 2.18:1 which even miserably fails the WCAG AA minimum contrast requirement. With active on a white background (#fcfcfc) the ratio is still a horrible 2.43:1.

I highly recommend improving the contrast here. Some possible suggestions:

1. Use a color that gives better contrast ratio, such as the color for "link",
2. Or better, use boldface type for unread messages.

KMail version 5.5.3
Comment 1 Michael D 2017-08-01 08:15:50 UTC
To be clear about suggestion (2), I meant use boldface type and the "normal text" color, a black, i.e. 31363b.
Comment 2 Justin Zobel 2022-11-06 09:25:04 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-21 05:14:50 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Michael D 2022-11-21 07:29:05 UTC
The bug is still reproducible.
Comment 5 Bug Janitor Service 2022-12-06 05:16:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-12-21 05:19:14 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!