Revisions and Commits
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T5824 Kleopatra: Full accessibility support | ||
| Resolved | • ikloecker | T6073 Kleopatra: Fix issues with high contrast resp. inverted color scheme |
Event Timeline
Note to self: On Windows, we need to check whether the high-contrast mode is enabled. If yes, then we must not use any custom colors. KColorScheme doesn't help here.
If the high-contrast mode is active (on Windows), then we disable the usage of custom colors in Kleopatra. This avoids problems with too low contrast due to the custom colors.
For testing purposes, high-contrast mode can be forced by setting the environment variable KLEO_HIGH_CONTRAST_MODE to 1.
There may still be problems with low contrast, if the user selects a "high-contrast" color scheme instead of activating the high-contrast mode.
Most things look good to me, it was automatically enabled when I switched Windows to high contrast mode. The only thing I noticed is that the fields where we explicitly set the background may not look to readable. Especially the Sign&Encrypt buttons because there we don't set the text color.
Did you restart Kleopatra after enabling the high contrast mode? I have implemented that Kleopatra doesn't change/set any background or foreground colors if high contrast mode is detected. Maybe the detection (in SystemInfo::isHighContrastModeActive) doesn't work.
You can check how it should look like by setting the environment variable KLEO_HIGH_CONTRAST_MODE to 1.
On windows the main window looks ok with high contrast mode black. But with dark backgrounds some items in other windows are not readable:
With setting "contrast white" everything in that window is readable.
