Triple-C

Files

T

shadowdaoandClaude Opus 5 aa0a574091 Announce unavailable controls instead of hiding them behind disabled

Native `disabled` removes an element from the tab order and from the
accessibility tree, so any explanation of why a control cannot be used is
delivered only to a sighted user with a mouse. `useUnavailable` is the way
out: `aria-disabled` keeps the control focusable and announced,
`aria-describedby` carries the reason, and — because `aria-disabled` is
advisory and blocks nothing — the hook hands back the click and Enter/Space
guards along with the attributes, so a call site cannot take the
announcement without the guard.

`Button` gets it as an opt-in `unavailable` / `unavailableReason` pair.
Opt-in matters: 37 files render this button and none of them change. The
`aria-disabled:` class mirrors exist because Tailwind's `disabled:` variant
only matches the native attribute, which this pattern deliberately omits.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011YPqHpjV4EL6RNEwrRKqQm

2026-09-02 09:08:50 -07:00

public

Give the app a mark that survives being 16 pixels tall

2026-08-11 12:01:39 -07:00

src

Announce unavailable controls instead of hiding them behind disabled

2026-09-02 09:08:50 -07:00

src-tauri

Fix terminal input reordering and Linux terminal rendering

2026-08-28 12:51:18 -07:00

index.html

Give the app a mark that survives being 16 pixels tall