-
Notifications
You must be signed in to change notification settings - Fork 509
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
Update trace colors for accessibility #632
Conversation
As of yesterday, the plan was to backport this to preview 1 as well once approved |
/backport to release/8.0-preview1 |
Started backporting to release/8.0-preview1: https://github.com/dotnet/aspire/actions/runs/6728052386 |
@tlmii backporting to release/8.0-preview1 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Patch format detection failed.
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
@tlmii an error occurred while backporting to release/8.0-preview1, please check the run log for details! Error: git am failed, most likely due to a merge conflict. |
Small modifications to the text color in a few areas of the traces and trace details pages.
This updates the text colors in the following places to ensure proper contrast:
The actual color changes are minimal. In all cases, both light and dark mode, we were close, but not quite. Before/After screenshots don't show any obvious difference unless you look really hard.
These changes impact both light and dark mode even though I've only shown dark mode above. I used the same setup that @JamesNK implemented for the metrics colors to handle the light/dark toggling given we're creating new variables.
This partially resolves #77, and I'm going to split off the remaining items I found into separate issues because they need more design discussion and potentially a11y team involvement.