A few projects that can help you get started on your accessibility journey.
Give it one colour and get a full, accessible palette back: 50–950 ramps for nine hues and two greys, lined up so every colour in a column has the same lightness and the same contrast.
That gives you one rule for the whole palette — how many steps apart two colours must be to pass 4.5:1 for text and 3:1 for icons. Export as CSS, JSON, or a design.md of light and dark mode rules for your AI builder.
VibeMagic converts your design system into an instruction file that AI coding tools can follow — and when it does, it automatically enforces accessibility labels and contrast ratios. Accessibility compliance becomes the default output, not a post-build checklist.
It also keeps the AI agent aligned with your design system, so generated code follows your standards from the start. Free to use.
An audit that dumps 400 issues on a team helps no one. The SUC Score framework gives every finding a severity rating — Suboptimal, Unusable, or Comprehension-breaking — so teams know what to fix first.
Watch this A11y Talks webinar to see how the framework works and how to apply it to your own audits. The research has continued since, and the latest version is now published as a field guide.
Platform-specific implementation guidance for WCAG success criteria — Android, iOS, Flutter, React Native, and more, one guideline at a time.
Teams that consider accessibility at the design stage see a 67% drop in compliance issues found during testing. This handbook is built for that stage.
A filterable WCAG 2.2 database — by compliance level, disability type, and component — so designers can catch issues before an auditor does.
Includes
Impact sizing means estimating the size of the crater inaccessibility makes — measured in revenue lost, users excluded, or fines incurred. This tool makes that calculation concrete.
The bundle gives you the theory behind quantifying inaccessibility at the dawn of EAA, plus an embedded calculator to estimate lost revenue from untapped markets or legal exposure.
WCAG is dense. This book cuts through it with straightforward rituals for mobile teams — practical methods for ensuring usability with TalkBack and VoiceOver, written like a doctor's prescription rather than a compliance manual.
Written for designers, product managers, design system teams, UI engineers, and product owners.
As the global population ages and dependence on digital products grows, designing for elderly users is no longer optional. This free resource explores how to make mobile applications work for the people we will all become.
A collection of all the answers you need to get BEFORE you can start building your own design system in your organisation. This Notion document focuses on the "WHY" aspects of the design system rather than the "HOW" to build one.
This publication covers details about setting up the design system, managing the launches, setting up KPIs as well as cases where one should not build a design system.
