doc_id: computer-use-ui-coverage title: “Computer Use Semantic UI Coverage” language: en source_language: en implementation_status: current document_status: current translation_status: source-only last_verified: 2026-09-11 owners:
Status: maintained source and runtime inventory for Maka Desktop's Computer Use target, state, focus, action and effect semantics.
This document defines what “covered” means for Computer Use operability. A page is not complete merely because it renders or because every button has a non-empty name. Critical surfaces must expose an unambiguous target, state, keyboard/focus behavior, and an observable effect.
This gate is not a claim of complete WCAG conformance or complete assistive technology behavior. In particular, live-region and announcement completeness are not measured here; they require separate accessibility testing.
| Surface | Runtime states | Semantic actions and effects |
|---|---|---|
| Settings | Top-level navigation entries are covered through the Storybook settings-pages stories; provider list/detail/catalog/add, subagent editor, memory populated, permission diagnostics, import empty/ready, usage variants, Daily Review selector and narrow states are in Storybook (the Electron-side dynamic enumeration was retired by #4803) | Navigation exposes aria-current; focused nested stories exercise dialogs, disclosures, selectors and editors |
| Extensions | Skills empty/installed/bundled/update/disabled/narrow/inspector; MCP setup/marketplace/configured/inspector/editor/failure/narrow | Page selection, inspector/editor opening and actionable-node identity |
| Scheduled work | Empty/configured/long/narrow/task inspector; Daily Review loading/error/refreshing/report | Task selection, dialog focus, selector state and report actions |
| Conversation shell | New task, settled conversation, streaming, permission wait, native conversation, modes, context and inline completion | Composer submit effect, unique per-task and per-turn actions, current regions and workbar selection |
| Workbar | Launcher plus side chat, changes, active terminal, browser chrome, files, tasks and trace states | Selected tabs, terminal input reaches the PTY bridge, browser navigation reaches the browser bridge |
| Dialogs and overlays | Rename, scheduled-task form, Mermaid fullscreen, side-chat close, onboarding QR, WeChat QR, Runtime Host SSH and remote directory chooser | Dialog naming/focus, rename callback, close confirmation, SSH input, directory navigation and registration |
| Generated content | Markdown, tool output, attachments, Mermaid and HTML artifact iframe | Scoped copy actions, fullscreen dialog and sandboxed iframe semantics |
| Embedded browser page | Live WebContentsView on a loopback fixture | Separate observe -> semantic ref -> fill/click -> business-effect smoke through the production browser bridge |
The Storybook catalog is exhaustive for its source-defined entries and the smoke runner carries a required Computer Use story manifest for critical runtime boundaries. The Electron-side broad route inventory (a spec that dynamically enumerated settings navigation, then modules, global overlays, conversations and all workbar entry points) was retired by #4803 rather than relocated; the surviving Electron journeys cover revision, WorkHub and draft-focus boundaries only.
Every measured final state fails on:
main landmark;aria-hidden surface;Critical stories additionally assert action-specific effects. (An Electron variant that waited for the specifically named prior dialog to close before auditing the next one was part of the retired route-inventory spec; the surviving journeys do not carry it.) Transport success or a generic dialog match alone is not accepted.
Repeated message and answer actions use a bounded excerpt of visible text plus a stable human-readable timestamp. Opaque storage IDs remain machine data and are not spoken as the user-facing differentiator.
WebContentsView; it is validated through its production semantic snapshot/action bridge, not falsely claimed as part of the renderer tree.screenReaderMode and have active PTY and SSH input fixtures.The product adds no accessibility dependency, production AX/DOM walker, global MutationObserver, timer, polling loop, OCR model or hidden duplicate agent UI. Semantic names and state are emitted by the existing React render. All full-tree walking, duplicate detection and inventory enforcement run only in tests and developer tooling. Existing lazy module, workbar and dialog loading remains unchanged.