hermes - 💡(How to fix) Fix [Feature]: Dashboard UI has poor contrast, making it very straining to read [1 comments, 2 participants]

Problem or Use Case

Issue Description

When using the Hermes Agent Dashboard, I noticed that the overall contrast between text and background is quite low (e.g., light gray text on white or light backgrounds). This makes it very difficult and tiring to read tables, logs, or configuration information. During extended use, eye fatigue becomes significant.

Impact

Poor readability — I have to lean in or squint to see clearly

Almost unusable under bright ambient light (e.g., daytime, near windows) or on older displays

Not friendly to users with visual impairments or those sensitive to low contrast

Suggestion Would it be possible to improve the contrast of the Dashboard theme? For example:

Darken the primary text color, or provide a dark / high-contrast theme option

Reduce the luminance similarity between gray text and the background

Add an optional "high contrast mode"

Environment

Hermes Agent version: v0.13.0 (2026.5.7)

Browser: [Chrome / Edge / Firefox / etc.]

OS: [Windows / macOS / Linux]

Thank you for your continued work on this great project!

Proposed Solution

Adjust default theme colors

Change primary text from light gray (e.g., #9ca3af) to a darker, more readable color like #1f2937 (dark gray) or #111827 (near black) on light backgrounds.

Ensure table rows, log lines, and configuration labels meet WCAG 2.1 AA standards (contrast ratio ≥ 4.5:1 for normal text).

Increase the contrast of secondary/subtle text (e.g., timestamps, metadata) from around #d1d5db to at least #6b7280.

Add a built-in high-contrast theme

Provide an optional theme named "high-contrast" (or "accessible") available in Dashboard settings.

This theme would use black (#000000) or near-black text on white/off-white backgrounds, with distinct borders and no low-opacity overlays.

Alternatives Considered

No response

Feature Type

Developer experience (tests, docs, CI)

Scope

None

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)