You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A browser click cannot assert CERTAIN, and the graph takes keyboard input
Three findings from operating the UI.
The web form could write CERTAIN with an empty rationale. In the store that
sat level with an OFAC designation --- and `docs/data-sources.md` says the
ceilings are enforced in code rather than merely documented, and that only a
published legal fact may assert CERTAIN. The form even labels the field
"why --- required below medium" and then did not require it. Now capped at
HIGH, and above MEDIUM needs a reason. The reply says when it lowered a
claim and why: a silent downgrade is its own defect, because the writer
believes the store holds CERTAIN and it does not.
Twenty-seven graph nodes, none in the tab order. Selecting an address is the
primary interaction of this tool and it was reachable only by pointing at
it. The roster list gave a keyboard path to the same action, but a graph
nobody can enter is not an accessible graph --- it is a picture with a
workaround beside it. Nodes are now buttons with labels that include the
address and, for a frontier, the fact that nobody looked past it. That last
part matters: the dashed border carries the difference between "the money
stopped" and "we stopped", and a dashed border is invisible to a reader who
cannot see it.
Focus was invisible everywhere --- the reset removed the browser default and
nothing replaced it, so a keyboard user could cross 79 controls without ever
seeing where they were.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FXWQ25VgFeMuuMhGWjvdof
0 commit comments