undefined | Better HN

0 pointsgedy2y ago0 comments

> One semi-objective thing we lost was accessibility.

TBH that's not a framework vs HTML issue, that's just sloppy or inexperienced devs

0 comments

4 comments · 2 top-level

chii2y ago· 2 in thread

I argue that it is a framework issue.

If the rendering framework doesn't support accessibility as a first class citizen (or better yet, automatically creates/makes accessibility part of what is rendered), then the framework is not suitable for production use.

LudwigNagasena2y ago

React simply diffs the DOM and updates it in an efficient way. If you are putting weird divs instead of anchors and buttons (or instead of special components provided by a React-based framework), that's entirely on you.

chii2y ago

if you're using react and then hand roll custom components and don't do accessibility, then it's just as bad as choosing a component framework which doesn't do accessibility. I am not talking about react (or any framework directly) specifically.

> entirely on you

of course - choosing a framework or hand rolling one makes no difference. It's still not production ready, if it doesn't have accessibility built in.

1 more reply

matijsvzuijlen2y ago

What could the frameworks do to make it more natural for inexperienced developers to do the right thing?

j / k navigate · click thread line to collapse