Outstanding: Verify Reduce Transparency and add opaque fallback #26

Closed
opened 2026-08-22 04:18:10 +00:00 by kayg · 2 comments
Owner

Current state

Outstanding. Reduce Transparency has no verified behavior in the current app, and there is no explicit opaque fallback for users who disable transparency. The appearance work currently depends on Liquid Glass and related materials, so the accessibility setting needs a deliberate, testable policy.

Acceptance criteria

  • Verify the observed behavior with Reduce Transparency enabled on supported macOS versions.
  • Provide an explicit opaque, legible fallback for window, toolbar, transcript, composer, and other glass/material surfaces.
  • Ensure controls and text retain sufficient contrast and no content depends on desktop refraction when the fallback is active.
  • Cover the setting transition and relaunch behavior, and document any OS limitations rather than claiming unverified support.
## Current state Outstanding. Reduce Transparency has no verified behavior in the current app, and there is no explicit opaque fallback for users who disable transparency. The appearance work currently depends on Liquid Glass and related materials, so the accessibility setting needs a deliberate, testable policy. ## Acceptance criteria - Verify the observed behavior with Reduce Transparency enabled on supported macOS versions. - Provide an explicit opaque, legible fallback for window, toolbar, transcript, composer, and other glass/material surfaces. - Ensure controls and text retain sufficient contrast and no content depends on desktop refraction when the fallback is active. - Cover the setting transition and relaunch behavior, and document any OS limitations rather than claiming unverified support.
Author
Owner

Judgement: keep this issue open as a narrower, actionable slice of the broader accessibility audit in #13, not a duplicate. #13 remains the audit/remediation authority; this issue focuses specifically on verifying Reduce Transparency and implementing an explicit opaque fallback for every glass/material surface, including transition and relaunch behavior. Cross-reference added to #13.

Judgement: keep this issue open as a narrower, actionable slice of the broader accessibility audit in #13, not a duplicate. #13 remains the audit/remediation authority; this issue focuses specifically on verifying Reduce Transparency and implementing an explicit opaque fallback for every glass/material surface, including transition and relaunch behavior. Cross-reference added to #13.
Author
Owner

User verification: with Reduce Transparency enabled, the complete Hermternal window became opaque and legible across the existing glass/material surfaces, including the sidebar, detail view, titlebar controls, and composer. Screenshot: https://img.kayg.org/u/0cLKx5.png. The system handles these existing surfaces, so no custom fallback is needed for v0.0.1. Closing #26 as satisfied.

User verification: with Reduce Transparency enabled, the complete Hermternal window became opaque and legible across the existing glass/material surfaces, including the sidebar, detail view, titlebar controls, and composer. Screenshot: https://img.kayg.org/u/0cLKx5.png. The system handles these existing surfaces, so no custom fallback is needed for v0.0.1. Closing #26 as satisfied.
kayg closed this issue 2026-08-22 07:57:20 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/hermternal-apple#26
No description provided.