> <div className="button" onClick={handler}>
> and it immedaitely sticks out as a mistake. Because its easier to statically understand these mistakes, theres even tooling to automate detecting some of them as you type https://www.npmjs.com/package/eslint-plugin-jsx-a11y
I'm not sure how you got that out of
> I have seen an increase in unknowingly doing so by importing a calendar widget or similar without reviewing it.
I'm referring to:
<div class="div-button" onclick="clickHandler()" />
VS: <SomeGreatNpmWidget onClick={clickHandler} />
The point of using components is so that you don't have to look under the covers to understand them at a high level, but that also means if you don't look you don't see how they're breaking accessibility.> Using React or whatever does not prevent you from doing this, and in fact makes it less obvious to anyone doing a cursory review
Sure. From that level it might not be apparent, but within that component the mistake would be immediately obvious, on a cursory glance. Again, I don’t think React or whatever makes this less obvious.
But really, this just isn’t a problem I’ve seen in practice. Because of good tooling, and the ease of doing things the right way, I think the majority do it well. Those that don’t were going to fuck it up regardless of the framework or paradigm.