Hacker News Reader

And no-JS HTML built as div soup is likely worse for accessibility than thoughtfully written React. So React itself has no bearing on it.

My take is that it's the growing complexity of web development (yes, React has some responsibility here), combined with the constant influx of new developers, that's largely to blame for any overall proportional loss in the practice of accessible markup.

I agree. Another thing to consider is that React makes it frictionless to import custom components, instead of attempting to re-write common UI patterns from scratch.

If a React dev leans on an accessible UI framework like Chakra, or Headless UI, or React-Aria, they're probably better off from an accessibility perspective than a dev that tries to implement WAI guidelines from scratch.

And? The point of the parent was that either of those are better than native - doesn't matter how much div soup you have, at least the information exists, unlike the bucket of raw pixels that're all you get from native UIs sometimes.

Desktop UI frameworks are a bit of a mess. Though truly OS native should be the most accessible of all.

This statement is practically a tautology