You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported by VIPER, there are issues with colors used for text in the Events table, particularly for Errors which use a red color. These colors are defined in SCSS files in the open repo, hence this issue. This is a problem for mission-critical information, so this is a blocker.
Colors should be adjusted in all themes and smoke tested for a11y conformance.
The text was updated successfully, but these errors were encountered:
Reference images show examples of all the different event color levels (yellow, red, purple, orange) in Espresso and Snow themes.
View Events data in a way that allows you to see all the available levels of events in your deployment.
Verify that the table's view corresponds with the matching theme reference image below.
If you have the Wave accessibility plugin installed, enable that and verify that there are no Contrast violations in the table's view area. IMPORTANT: this issue depends on certain key theme colors (like the page body background color) having been updated via Fix constrast for accessibility #7315. If those changes aren't merged, then this step won't pass verification.
Switch themes using the devtools Console command openmct.install(openmct.plugins.Snow()) or openmct.install(openmct.plugins.Espresso()).
As reported by VIPER, there are issues with colors used for text in the Events table, particularly for Errors which use a red color. These colors are defined in SCSS files in the open repo, hence this issue. This is a problem for mission-critical information, so this is a blocker.
Colors should be adjusted in all themes and smoke tested for a11y conformance.
The text was updated successfully, but these errors were encountered: