Check your project
Choose the configured dialog and measurement targets. See the actual result, expected rule, viewport and anything the check could not verify.
From finding to decision
A useful next step.
Evidence you can revisit.
For people building websites with coding agents, and teams maintaining shared interface rules.
These Studio upgrades are included in the v0.9.0 CLI archive. Get the verified release ↗
Individual builders
Give your agent
a concrete finding.
You need a trusted local static HTML or React/Vite project and Node. Studio guides supported setup. It cannot check any public website just from its URL.
Prepare a focused brief
Select findings and review the brief before copying. It carries source and rule identifiers, relative file labels and recheck steps. No AI service is contacted.
Review and recheck
Use your existing coding agent to propose changes. Review those changes, rebuild Vite when needed, and run the checks again. The brief itself grants no write authority.
Try the complete local example
stylecon demo /absolute/path/to/new-demo
stylecon studio /absolute/path/to/new-demo --evidence /absolute/path/to/private-evidenceCreate the private evidence directory first, outside the demo workspace. Select project, run checks, and inspect the failing button. Select its finding, then choose Prepare selected findings.
The supplied correction also lets you try preview, apply, recheck and undo without an AI account. Your coding agent may have its own costs.
Teams & enterprise evaluation
Agree on the rules.
Keep the evidence scoped.
Start with one supported component and an advisory check. Keep policy approval and production decisions in your existing repository workflow.
Review team rules
Create and export a constitution. In Studio, create a snapshot, review the old and proposed rules, then adopt its exact hash for the selected project.
Revisit the evidence
Private history survives Studio restarts. Compare runs with the same configuration, rules and recorded coverage. Different rules cannot erase an earlier failure.
Review a pull request
The existing CI workflow binds evidence to Git source and shows new, existing, resolved and incomplete findings. Reviewers decide how it affects the PR.
What stays local
Studio listens on loopback. Reports and history stay in the private directory you choose. No project account, telemetry or automatic cloud upload is required.
Briefs can contain private project text. Review them before sharing. History checksums detect accidental changes; they are not signed attestations.
What an evaluation must establish
Confirm support for your component, compare results with your current tests, and record unresolved coverage. Check whether the workflow saves your team effort on real changes.
This local tool does not supply hosted workspaces, organization identity, SSO, role management, compliance certification or a service-level agreement.
For clients & reviewers
Open the results.
No tools to install.
The developer prepares an offline review packet in Studio. You receive a readable HTML document with every recorded outcome and visible evidence gaps.
Less project detail to disclose
Numbered elements replace private target names. Measurements, viewports and evidence identifiers stay visible; source paths and free-form diagnostics are omitted. Ask the sender which page and elements the numbers describe, and request context for missing values.
The sender reviews the complete packet before downloading. It opens without scripts or network access. It is a historical observation, not a live check, signed approval or full accessibility audit.
Review packet workflow ↗ · Included in v0.9.0.