-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
Links show too little contrast in dark mode #3477
Comments
(Just for reference: the two blue tints with 4.6 contrast each would be 217aba (for light) and 3c9add (for dark).) |
Any update on this? I assume it's a question of consideration, not feasibility. |
Chiming in, this is an accessibility issue for me. As I understand it, people with cataracts lose some of their ability to perceive blue. |
It's really hard to reading in the app at night in the bedroom. |
Fixes: #3477 This tweaks two colors: * for the dark theme a new slightly darker (timeline) background is used. * for the light theme a darker shade of blue is used as highlight color (`colorPrimary` and `colorSecondary`) Additional change: * Use green and red more consistent: use existing colors for the diff display; move the new light variants to colors.xml like all colors
I am using Tusky daily and I really like this app. What I see as an issue is the dark theme (night theme) in combination with links (hashtags, URLs) etc, as these have too little contrast to be readable in a night time setting.
I tried to figure it out and it seems that the link color is
tusky_blue
according toTusky/app/src/main/res/values/colors.xml
Line 3 in 8c519af
As far as I can see, the background in posts is #282c37 (
tusky_grey_20
).According to WebAIM, those two colors have a contrast of 4.04:1 and fails WCAG AAA in both normal and large text.
I propose to adapt the link color or the background color, to increase the contrast. For example, the link color #83BEF1 would pass all four checks with WebAIM.
Tusky Version: 21.0
Android Version: 13
Android Device: Pixel 7
I searched or browsed the repo’s other issues to ensure this is not a duplicate.
The text was updated successfully, but these errors were encountered: