Methinks we have a different definition of accessibility and are required to meet different norms. I deal with clients who are in COURT for this stuff. Public utilities, banks, government organizations, medical, and so forth. Regional laws both state and federal, including the US ADA and UK EQA make things like “accessible web applications” NOT EVEN BE A FLIPPING THING THAT EXISTS!

That you would even say “accessible web application” is basically bragging you have no idea of accessibility minimums, given such crapplets are INHERENTLY inaccessible either because they’re standalone apps as full stack, or if used on a website have ZERO graceful degradation scripting off.

And that’s before we talk about how on the back end react ACTIVELY promotes dated markup techniques that it then compiles out, at which point why the hell use it in the first place? It just teaches people to use outmoded crap like “onevent” attributes and other such ignorant trash. Much akin to how the halfwit HTML/CSS frameworks like bootcrap or arsebreeze drag coding practices back to the worst of HTML 3.2 with their derpy presentational classes.

I have NEVER seen anything built with React that even comes close to the most basic of accessibility minimums for an actual website. Particularly since it’s oft used to do things client-side that have no business being handled client-side and/or without any graceful degradation plan. The result typically tells users on screen readers and braille readers to go F*** themselves.

Which isn’t exactly a great business plan, no matter how many scripttard fanboys cream their panties over “JavaScript for Nothing”

JS for nothing and your scripts for free. That ain’t workin’, that’s not how you do it. Lemme tell ya, these guys ARE dumb.

As I said in other replies, as I’ve said for over a decade, everything I’ve ever seen done with JS frameworks — jquery, angular, react, vue, etc, etc, etc — falls into three categories.

  1. Stuff that would be as much or even less code without the framework, NOT counting the framework size against said total.
  2. Stuff that’s none of JavaScript’s business and could be handled by HTML/CSS all on their lonesome.
  3. Stuff that has ZERO huffing business on a website in the first damned place if you give a flying purple fish about accessibility, usability, maintainability, or anything else someone with actual abilities would care about.

It’s all junk. It’s not easier, it’s not simpler, it’s not better, and the results sure as the **** isn’t accessible. That you would even say they are blows my mind, because — and this is just my opinion — it means you don’t even know what accessibility is.

Because “web applications” sure as shine-ola aren’t it. Try using that incompetent trash on something like a Orbit or Smart Beetle. /FAIL/ hard.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store