Love Thy Keyboard
summary
Keyboard accessibility matters when an interface actually lets you tab, arrow, enter and space to do everything a mouse can do; demos show missing focus outlines, mouse‑only widgets, broken tab order, trapped focus in modals, and nonfunctional custom controls fixed by using semantic HTML not divs plus handlers. Practical tools demonstrated include using focus() to manage modal focus, role="button" only as fallback, aria-live for spoken updates, and a Chrome extension called focus indicator that exists and already has about 1,990 users.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:52Keyboard accessibility matters
- 8:29Keyboard accessibility issues
- 13:33Semantic HTML fixes
- 17:56ARIA roles states properties
- 19:21Focus management dynamic UI
- 23:43Summary
related talks
25mStuck in a Focustrap: Mastering Keyboard Accessibility
45mIs Your Site Keyboard Accessible?
31mThree Cheers for Keyboard Accessibility
46mFocusing on Focus
34mFreak'n Keyboard Traps
28mYou're only supposed to blow the bloody doors off!
52mInclusive design challenges with UI widgets
35mBeyond the Screen: A Deep Dive into Linux Accessibility for Developers