0
Challenge · 75Architecture & State

Accessibility (ARIA)

Coreused in ~50% of apps

A div with onClick looks like a button and works with a mouse — but a keyboard user can't focus it, can't press it, and a screen reader announces nothing. Accessibility is how you build UI that everyone can operate, and in 2026 it is increasingly screened in interviews and required by law.

Core idea. Reach for semantic HTML first — it gives you roles, focus, and keyboard behavior for free. Add ARIA roles, labels, and state only to fill the gaps native elements can't, and make every interactive control keyboard-operable.
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