Skip to content

Studio: five controls fail the 3.0 contrast check #211

Open

Description

@AojdevStudio

Found by the verify-materialize-3d contrast sweep on #201 head cca2035 (dev-substrate run 20261108-023633).

Control Text Background Ratio
prompt placeholder #a9a9a9 #ffffff 2.35
"API key or token" placeholder #a9a9a9 #ffffff 2.35
"Proxy URL" placeholder #a9a9a9 #ffffff 2.35
Save button #959596 #fdfdfc 2.94
disabled send button #fadaca #f5bb9f 1.28

Ossie chose to merge #201 and fix these first in the UI polish pass. Done means wd.ts contrast passes on the start screen with the sign-in notice shown.

Activity

  1. pullfrog commented on Nov 8, 2026

    @pullfrog

    Overlap: #196 already tracks the prompt placeholder and disabled Send button. This issue also covers three sign-in notice controls, so it is broader rather than a full duplicate.

    Plan

    1. Coordinate with fix(studio): the start screen's prompt placeholder and disabled Send button measure below 3.0 contrast #196 to fix the shared composer once. In src/studio/studio.css, give the placeholder an explicit readable color and replace opacity fading on the disabled primary button with an opaque disabled palette. Check both the start and project composers.
    2. On the merged feat(studio): the window works on the sidecar's committed chats, and the claude -p runner is gone #201 code, inspect the sign-in form in src/studio/Waiting.tsx and its styles. Set explicit placeholder and Save button colors, preserving their enabled, disabled, and focus behavior. The current checkout predates feat(studio): the window works on the sidecar's committed chats, and the claude -p runner is gone #201, so confirm the exact selectors on the current main branch first.
    3. Run verify-materialize-3d and wd.ts contrast on the start screen with the sign-in notice shown, exercising the relevant button states. Verify all five controls and the full sweep without new baseline exceptions; capture screenshot proof for the eventual PR.

    The 3.0 sweep is a smoke check, not a WCAG AA text-contrast verdict: aim for 4.5:1 for normal active text and placeholders. Disabled controls are exempt from WCAG contrast requirements but remain in this issue’s acceptance criteria.

    Pullfrog  | Implement a fix ➔ | View workflow run | via Pullfrog | Using gpt-6.1-terra | 𝕏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    accessibilityBarrier affecting people with disabilitiesbugSomething isn't workingtypescript

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions