Design Systems
10 min read
How to start a design system without over-engineering it
You do not need a hundred-component library on day one. Here is the minimum viable system that pays for itself immediately.
design systemsstartupsprocess
Product Design
Accessibility is not a phase at the end. Built into the system, it costs almost nothing and makes the product better for everyone.
Teams treat accessibility as a tax because they leave it to the end, where it becomes a retrofit: an audit, a list of failures, and a scramble to fix them before launch. Move it into the system instead and it nearly disappears as a cost, because most of the work happens once, in the primitives, and every screen inherits it.
Here is how to hit WCAG 2.2 AA as a baseline your components guarantee, so your team spends its judgment on the experience above the floor rather than the floor itself.
The shift
If the primitives are accessible, most screens are accessible for free. Concretely: color pairs in your token system that meet contrast by default, so no one can accidentally ship unreadable text. Focus styles that ship with every interactive element, so keyboard users are never lost. Form fields wired to labels and error messaging as part of the component, not the page. And sensible target sizes built into buttons and controls.
Do this once and the accessible version becomes the default version. The team stops choosing accessibility screen by screen because the components already made the choice.
Written by
Jayesh Velossa
Founder & Creative Director
Automated checks catch contrast, missing labels, and structural issues. They do not catch whether the keyboard path makes sense, whether a screen reader announces things in a useful order, or whether an interaction is understandable without color. Keep a short human checklist for those: keyboard path, screen-reader labels and order, contrast, and motion-reduction. Reserve human testing for exactly the things tools cannot judge, and automate the rest in CI.
AA is the floor, not the trophy
WCAG 2.2 AA is the baseline your components should guarantee automatically. Spend your actual design judgment on the experience above it, not on re-earning the baseline every screen.
Accessible defaults are not a niche accommodation. Sufficient contrast helps everyone in bright sunlight. Clear focus states help every keyboard-heavy power user. Large enough targets help every thumb on a moving train. Labelled forms help everyone under stress. Designing for the edges reliably improves the middle.
Built into the system, accessibility stops being a phase with a cost and becomes a property of the product. That is the whole trick: move it early, make it structural, and it stops slowing anyone down.
None of this requires a specialist gatekeeper or a separate accessibility sprint. It requires accessible primitives, a short checklist for the human-judgment parts, and the discipline to keep the baseline in the components. Do that and WCAG 2.2 AA is just how your product is built.