DFDuncan Faulknerinduncanfaulkner.hashnode.dev·Jul 10 · 7 min readThe WCAG AA Checklist Every Angular Component Should Pass Before You ShipI've been writing Angular for ten years, and for most of them I treated accessibility the way nearly everyone does: as a thing I'd "get to" once the feature worked. It always lost the race to the dead00
DFDuncan Faulknerinduncanfaulkner.hashnode.dev·Jul 10 · 6 min readAXE Passes, But It's Still Unusable: The Accessibility Bugs Automated Tools Can't CatchThere's a particular kind of false confidence that comes from a green accessibility report. The CI check passes, the Lighthouse score says 100, the AXE panel is all ticks. You ship it. And somewhere, 00
DFDuncan Faulknerinduncanfaulkner.hashnode.dev·Jul 10 · 6 min readManaging Focus in Angular: Dialogs, Drawers and Route Changes Without Stranding Your UsersEvery accessibility checklist mentions focus management, and then moves on — as if it were one item. It isn't. It's a discipline, and it's the single thing that most often separates an app that techni00
DFDuncan Faulknerinduncanfaulkner.hashnode.dev·Jul 5 · 8 min readWhy I Built an Angular Component Library Where Accessibility Isn't a Backlog ItemI've been building with Angular for ten years, and in that time I've watched the same thing happen on nearly every project. A component gets built, it works with a mouse, it ships. Accessibility — key00
