Accessibility bugs rarely show up in a demo with a mouse. They show up when someone tabs through the page, listens through a screen reader, or clicks what the menu said was available. Each lesson is one place where the interface promised something the code did not keep.
If a UI shows a command as available, check it against the same rules the command will run with. Otherwise the menu offers actions that throw.
Read the lesson →Replacing a <button> with a div to avoid nesting means you now own everything the button did for free: focus, Enter and Space, disabled state, and not swallowing events meant for the real buttons inside it.
Yes/no questions from other reviews on this theme. Each one is quick to answer for your own app.
<button> inside another <button> or link?Want a senior reviewer to run these checks on your code? Ongoing pull-request review capacity →
We run reviews like these on real codebases. Tell us what you are building and we confirm scope before anything starts.
A link or short description of the code or system, what you want checked, your stack, and when you need the answer. No repository access is needed until scope is agreed.