Outstanding: Verify Reduce Transparency and add opaque fallback #26
Labels
No labels
delivered
outstanding
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
kayg/hermternal-apple#26
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.
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.