svenmany
macrumors 68030
I’ve been using macOS daily for decades, across both Intel and Apple Silicon eras, and I don’t say this lightly… macOS Tahoe represents a noticeable regression in basic usability and visual design discipline.
View attachment 2596425
This screenshot is a simple but telling example. In the Messages app, Dark Mode, macOS renders white text on a very light background, resulting in insufficient contrast and reduced legibility. This isn’t an edge case or an obscure preference setting... it’s a direct violation of long-established usability and accessibility principles.
At a minimum, Apple should be meeting:
Instead, Tahoe feels increasingly inconsistent, as if visual polish is being prioritized over functional clarity. Dark Mode, in particular, seems treated as a skin rather than a first-class design system... leading to situations where text becomes harder to read precisely when users choose Dark Mode to reduce eye strain.
- WCAG contrast guidelines
- Clear foreground/background separation
- Predictable visual hierarchies across light and dark modes
This issue isn’t isolated. Across Tahoe, there’s a growing pattern of:
Apple used to be the company that understood that good design is invisible… that it gets out of the way. Lately, macOS feels like it’s drifting toward aesthetics-first decisions that ignore real-world usage and professional workflows.
- Low-contrast UI elements
- Ambiguous visual cues
- Excessive translucency that undermines readability
- Visual effects competing with clarity
If Apple wants to continue positioning macOS as a productivity-first OS, these basics need to be addressed. Visual consistency, contrast, and legibility are not subjective preferences... they’re foundational to usable software.
Curious if others are seeing the same pattern in Tahoe, especially those running Dark Mode full-time.
I do run dark mode all the time.
There are bugs that will make your experience different than others. Even though others will claim it's ok for them, something subtle about how you arrived at the screen you're seeing might cause it to render differently.
An example on another thread that I brought up is a bug in System Settings. If it is launched in the usual fashion (from the Apple menu) all will be good. If it is launched from some other process (like a warning that some app wants to run in the background), then the translucency in the area around the search field will malfunction, making the text behind the field not fade enough to clearly read the contents of the field.
Independent of bugs, translucency seems to be inconsistent or dependent on things you wouldn't think matter. Some areas that are having their translucency adjusted are adjusted along with adjacent areas. Therefore, the content directly under a particular area might not be most affecting it. This will probably improve over time since the better Apple developers are probably working on it.
Just yesterday I decided to just turn it off in System Settings by turning on reduce transparency. But Apple ignores that setting in the Preview app. That's another aspect of their inconsistency - the applications they write use Liquid Glass inconsistently.

