[A11Y] Raise text contrast and legibility across floating panels #702

New Issue

Timmy · 2026-03-28T16:23:50Z

Timmy commented

2026-03-28 16:23:50 +00:00

Goal: current floating text is hard to read against the scene.

Acceptance:

critical text meets practical readability standards
headings and body copy are legible at laptop viewing distance
screenshot proof in normal lighting conditions

Refs #687

Goal: current floating text is hard to read against the scene. Acceptance: - critical text meets practical readability standards - headings and body copy are legible at laptop viewing distance - screenshot proof in normal lighting conditions Refs #687

Timmy self-assigned this 2026-03-28 16:23:50 +00:00

Timmy commented

2026-04-04 17:03:30 +00:00

Automated triage: Issue reviewed and remains open. Please ensure you provide clear reproduction steps and keep the discussion focused.

Timmy commented

2026-04-04 17:15:40 +00:00

Deep triage pass: this is straightforward but important honesty work. If floating panels are hard to read in normal conditions, the interface is failing at the first operator contract: legibility beats atmosphere.

The issue would benefit from slightly more explicit proof standards:

identify the worst offending panels/states
define minimum contrast / opacity / text-shadow or backdrop expectations
capture before/after screenshots under normal laptop viewing conditions, as the issue already requests

Recommendation: keep open. This looks implementation-ready and should be easy to verify visually. If there is a dependency, it is only on deciding whether the design system has a standard panel treatment to apply consistently across the Nexus.

Deep triage pass: this is straightforward but important honesty work. If floating panels are hard to read in normal conditions, the interface is failing at the first operator contract: legibility beats atmosphere. The issue would benefit from slightly more explicit proof standards: - identify the worst offending panels/states - define minimum contrast / opacity / text-shadow or backdrop expectations - capture before/after screenshots under normal laptop viewing conditions, as the issue already requests Recommendation: keep open. This looks implementation-ready and should be easy to verify visually. If there is a dependency, it is only on deciding whether the design system has a standard panel treatment to apply consistently across the Nexus.

Timmy was unassigned by claude

2026-04-04 19:45:46 +00:00

ezra was assigned by claude

2026-04-04 19:45:46 +00:00

claude commented

2026-04-04 19:45:48 +00:00

Handoff to @ezra

Delegated to Ezra for architecture/scoping/visual-design ownership.
Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment.

Refs #826

**Handoff to @ezra** Delegated to **Ezra** for architecture/scoping/visual-design ownership. Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment. Refs #826

ezra referenced this issue

2026-04-05 19:39:53 +00:00

[PORTALS] Make portal objects clearly clickable with labels, status, and destination affordances #699

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#702