undefined | Better HN

0 pointsrimantas10y ago0 comments

If your are optimizing for the development, you ar doing it wrong. So sad to see years of effort on making web more accessible thrown out of the window. How do react/angular/whatever sites work with assistive technologies like JAWS? The first thing learning about these frameworks should be when not to use them.

0 comments

2 comments · 2 top-level

bphogan10y ago

I spend a lot of time worrying about this because I consult on accessibility issues, I an an accessibility advocate, and I am a low vision computer user.

Provided that developers use the proper HTML tags and ARIA roles, there shouldn't be any different issues here than with other JS libraries.

However, I want to stress that React, Ember, and Angular are amazing tools for apps, but if you are using them just to render static content, you're just inviting all kinds of accessibility issues that server-side rendering solved years ago. Web servers are optimized to serve static content quickly. Sending JSON to the client so the client can render HTML for a blog post or news article seems pretty wasteful, and again, invites accessibility issues that don't need to be there.

Sir_Cmpwn10y ago

There's nothing about React that makes it worse for screen readers.

j / k navigate · click thread line to collapse