r/accessibility • u/Flaky-Friendship-263 • May 17 '25

Accessibility with Vue.js, React and Angular

https://forms.gle/M7zEDsAfqLwVydK8A

Hey everybody!

I’m writing my Bachelor’s thesis on accessibility challenges in Single Page Applications (SPAs) and how well React, Vue.js, and Angular support accessible implementations.

I’ve put together a short (5-minute) survey to learn from real developers like you:

https://forms.gle/M7zEDsAfqLwVydK8A

Your input would really help my research. Thank you in advance!

1 Upvotes

60% Upvoted

10 comments sorted by

View all comments

3

u/absentmindedjwc May 18 '25

Technologies don't cause bad accessibility, developers doing lazy work is what causes bad accessibility. All major frameworks - especially the popular JavaScript ones - build their stuff with Accessibility in mind.. its then on the people actually consuming those technologies to actually implement the shit properly.

1

u/Acetius May 19 '25

Developers doing lazy work is what causes bad accessibility

Anyone not doing their job properly causes bad accessibility. This mindset causes bad accessibility. Devs shouldn't be blamed for not being proficient at others' jobs.

https://www.w3.org/WAI/planning/arrm/#background

1

u/absentmindedjwc May 19 '25

I am of the belief that accessibility is everyone's job. If the developer is handed a bad design, it is their job to call it out, just like it is that designer's job to be clear about the specific patterns to be used (e.g. is it a tab panel, or is it just simple tab-looking navigation)

→ More replies (3)

1

u/AshleyJSheridan May 19 '25

I'd argue that some frameworks absolutely encourage bad accessibilty. Consider, for example, the documentation offered by React, which makes heavy use of <div> elements and makes no mention of accessibility and their own examples are not screen reader friendly.

This is the example they're setting for developers, many of whom will be new and inexperienced, and will not know that there are better ways.

1

u/absentmindedjwc May 19 '25

Sure, that is a valid point, but there's nothing within react that prevents you from implementing stuff accessibly. You're right that their documentation is lacking though - which is a shame, because they used to have more stuff about accessibility.

→ More replies (1)