Checklist ux conventions

ux-conventions

Generated by pnpm gen:checklist-status from docs/qa/platform-checklist/areas/*.json. ⛔ Do not edit this page — edits go to the area JSON and this page follows on the next run. This page is Checklist-ux-conventions.

Cross-cutting UX conventions — every write answers, every disabled control explains itself, labels over machine names (console and Studio)

3 active · 0 planned

Active (3)

id	title	priority	status	personas
ux-conventions.write-feedback	Every user-initiated write answers visibly — success names what changed, a refusal says why, and a no-op claims nothing	P1	active	admin (the platform admin seeded by --seed-admin), member (non-admin end user) for the record rows
ux-conventions.disabled-control-reason	Every disabled control explains itself — the reason shows on hover and on keyboard focus, and is exposed as an accessible description	P1	active	admin, member (non-admin) — for the disabled states only a non-privileged persona meets
ux-conventions.labels-over-machine-names	Where a label exists users see the label — machine names, raw ids and spec paths appear only as secondary text	P1	active	admin (Studio, Setup), member (console record surfaces)