Start with people
Understand users, goals, constraints, risks and what success looks like.
Public Standard · v0.1 · August 2026
Make digital products that hold up.
The By JTT Design Standard is a practical guide to product purpose, accessibility, interaction, content, AI-assisted work and production quality.
Principles
Start with what matters.
Good interfaces follow from a clear problem, sound evidence and realistic conditions.
Use evidence
Base important decisions on user needs, product requirements, platform guidance or a clear design reason.
Design real conditions
Include varied content, devices, states, errors and different ways of interacting.
Make it accessible
Build semantics, focus, contrast, zoom, motion and assistive-technology support into the product.
Reuse good solutions
Use established standards and mature systems before creating something new.
Test the real product
A screenshot is not proof. Validate the implementation people will actually use.
AI + agents
Keep automation understandable.
People should know what an AI system suggested, created, checked and actually changed.
Suggested → Generated → Inspected → Verified → Executed → Human-approved
Use clear states for meaningful actions. The stronger the consequence, the clearer the evidence and user control should be.
Inclusive design
Make access part of the product.
Design for different abilities, devices, preferences and environments from the start.
Interaction
Provide usable paths for keyboard, touch, pointer and assistive technology where relevant.
Content
Expect long text, errors, missing media, localisation and machine-generated content.
Adaptation
Support useful preferences without hiding meaning or taking control away from the user.
Evidence
State what was tested and what remains unknown. Do not turn an automated score into a promise.
For people using the standard
Go as deep as your work requires.
You can start with plain-language guidance and move into structured contracts and machine-readable rules when useful.
Starting out
Use the principles to frame a problem and make better design choices without learning a new vocabulary.
Try the Studio →Designing
Use contracts, states and rationale to keep important decisions clear as the interface develops.
Explore Contracts →Building
Use the implementation guidance for semantics, tokens, responsive behaviour and validation.
Read the documentation →Working with AI
Use the machine-readable resources to give AI systems explicit requirements and boundaries.
See the agent guidance →Versioning
v0.1 is a working version.
Changes should be supported by research, testing, production evidence or useful feedback. Material changes record what changed and why.