0
Challenge · 17Data & Reads
Accessibility & semantic forms
Formsused in ~80% of apps
This is the part of the job that separates people who ship to real users from people who only ship to themselves. Roughly one in five users needs assistive tech, every government and enterprise contract requires it, and certifications (and interviewers) test it directly. Worse: an inaccessible form is also a broken form — wrong labels, lost focus, and client-only validation fail keyboard and screen-reader users AND let bad data into your database.
Core idea. Use the right HTML element for the job, give every input a real associated <label>, validate on the SERVER (the client is a convenience, never the gatekeeper), and manage focus when content changes. Accessibility is not a plugin you add at the end — it is the semantics of the markup you write first.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
BUILD THE SAME WIDGET TWO WAYS
<PostCard />NOT ACCESSIBLE
Likediv
Commentsdiv
SCREEN READER HEARS
Press Tab to move keyboard focus into the widget.
ACCESSIBILITY TREE NODE
(generic div — no role, no name, no state)
DRIVE IT BY KEYBOARD
tip: click the widget, then use your real keyboard
Same pixels, two builds. In div soup the mouse works but Tab can't enter and the screen reader hears silence. In semantic + ARIA the button is focusable, operable by Enter/Space, and announced with role + name + state — for free.
↑ play a little first, then dig in