Validate accessible responsive views and semantic agreement with producer CLI #10

New issue

Open

opened 2026-10-04 23:04:49 +00:00 by kilo · 0 comments

kilo commented

2026-10-04 23:04:49 +00:00

Member

Goal

Owner: Console UX/accessibility. Make supported operational states readable with keyboard/assistive technology and consistent with producer facts.

Why / Current Evidence

Convenience must not require logs, color interpretation or dashboard navigation. Console seed d6468f3 has no operational views; bootstrap will provide only a semantic non-operational scaffold. Producer CLI presentation remains producer-owned. Source sections 4-6,10,12; G08/G10/G13.

Scope / Non-Goals

Proposed WCAG2.2 AA target, semantic landmarks/headings/forms, visible focus/skip links, responsive layouts, progressive disclosure with exact IDs, accessible loading/errors/status and meaningful timestamps. No terminal framework, custom widgets or independent business logic.

Acceptance Criteria

Real keyboard and assistive-technology walkthroughs plus automated checks for normal/empty/stale/disconnected/denied/unsupported/unknown views on reviewed desktop/mobile browser matrix.
Status/required action understandable without color; no hover-only controls, misleading progress percentages or high-volume token live-region spam; reduced motion respected.
CLI and Console show same business facts at identical producer revision/policy; observation-time differences remain visible rather than reconciled with new UI logic.
IDs/raw evidence remain inspectable alongside labels; permissions cannot be inferred from hidden controls.
Zoom/reflow, focus restoration, errors and external navigation verified; measurable targets documented as proposals with assumptions, not invented guarantees.

Constraints

Safe rendering/private metadata minimization, no external font/assets needed. Unknown versions/fields explicit; migrations preserve accessible labels/state semantics. Reuse browser semantics and tested permissive primitives after exact license/security check. Priority P2, acceptance of every operational view, not late polish. No producer implementation/CLI reformatting; browser access separately authorized, no inference.

Links / Dependencies

Parent #1; Console #2/#3/#4/#5/#6/#7 and navigation issue. Producer source revisions defined by #2; Kernel Creatidy/creatidy-kernel#57; Router BioMedical-IT/scarcity-router#183; MI Creatidy/model-intelligence#16.

## Goal Owner: Console UX/accessibility. Make supported operational states readable with keyboard/assistive technology and consistent with producer facts. ## Why / Current Evidence Convenience must not require logs, color interpretation or dashboard navigation. Console seed d6468f3 has no operational views; bootstrap will provide only a semantic non-operational scaffold. Producer CLI presentation remains producer-owned. Source sections 4-6,10,12; G08/G10/G13. ## Scope / Non-Goals Proposed WCAG2.2 AA target, semantic landmarks/headings/forms, visible focus/skip links, responsive layouts, progressive disclosure with exact IDs, accessible loading/errors/status and meaningful timestamps. No terminal framework, custom widgets or independent business logic. ## Acceptance Criteria - Real keyboard and assistive-technology walkthroughs plus automated checks for normal/empty/stale/disconnected/denied/unsupported/unknown views on reviewed desktop/mobile browser matrix. - Status/required action understandable without color; no hover-only controls, misleading progress percentages or high-volume token live-region spam; reduced motion respected. - CLI and Console show same business facts at identical producer revision/policy; observation-time differences remain visible rather than reconciled with new UI logic. - IDs/raw evidence remain inspectable alongside labels; permissions cannot be inferred from hidden controls. - Zoom/reflow, focus restoration, errors and external navigation verified; measurable targets documented as proposals with assumptions, not invented guarantees. ## Constraints Safe rendering/private metadata minimization, no external font/assets needed. Unknown versions/fields explicit; migrations preserve accessible labels/state semantics. Reuse browser semantics and tested permissive primitives after exact license/security check. Priority P2, acceptance of every operational view, not late polish. No producer implementation/CLI reformatting; browser access separately authorized, no inference. ## Links / Dependencies Parent #1; Console #2/#3/#4/#5/#6/#7 and navigation issue. Producer source revisions defined by #2; Kernel https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/57; Router https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/183; MI https://forgejo.creatidy.com/Creatidy/model-intelligence/issues/16.

kilo added a new dependency

2026-10-04 23:05:48 +00:00

#2 Define supported producer reads and the browser authentication boundary

kilo referenced this issue

2026-10-04 23:05:48 +00:00

Deliver cross-product overview and exact Kernel task evidence drill-down #4

kilo referenced this issue

2026-10-04 23:05:48 +00:00

Reuse Router administration, Forgejo and supported harness navigation safely #8

~~kilo referenced this issue 2026-10-04 23:26:31 +00:00~~

Bootstrap Creatidy Console: architecture, repository foundation and integration backlog #15

~~kilo referenced this issue 2026-10-04 23:27:33 +00:00~~