C · thread
Accessibility
Building both clients to a real accessibility standard — WCAG targets, platform accessibility APIs, testing with assistive tech, and the legal exposure of skipping it.
8 decision topics in this thread — every topic gives a recommended default, the reasoning, and what flips it. Titles and dates below are free; the verdicts and full topics are the paid masterclass (a few showcase verdicts are shown in full).
| ID | Topic | Verdict | Verified |
|---|---|---|---|
| A11Y-001 | Conformance target (WCAG 2.2 AA, EAA exposure) | Build both your mobile and desktop clients to WCAG 2.2 Level AA from the start, but assert formal conformance to WCAG 2.1 Level AA — the level your binding law actually names — and list 2.2 as your stated roadmap. | 2026-06-26 |
| A11Y-002 | Accessibility designed in | �e9f6e; verdict in the full masterclass | 2026-06-26 |
| A11Y-003 | Screen-reader support (VoiceOver / TalkBack) | �e9f6e; verdict in the full masterclass | 2026-06-26 |
| A11Y-004 | Dynamic Type, scaling & keyboard navigation | �e9f6e; verdict in the full masterclass | 2026-06-26 |
| A11Y-005 | Contrast & color-blind-safe visuals | �e9f6e; verdict in the full masterclass | 2026-06-26 |
| A11Y-006 | Accessibility testing & CI checks | �e9f6e; verdict in the full masterclass | 2026-06-26 |
| A11Y-007 | Accessibility audit & remediation | �e9f6e; verdict in the full masterclass | 2026-06-26 |
| A11Y-008 | Apple Accessibility Nutrition Labels | �e9f6e; verdict in the full masterclass | 2026-06-26 |
Each topic behind these titles is a full worked decision: what it is, the recommended default, why, what flips it, how to execute it with your coding agent — cited and dated.
Read a full topic free →Launching soon — read a free chapter