this post was submitted on 05 May 2025
88 points (94.9% liked)

Programming

19986 readers
365 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Static_Rocket@lemmy.world 4 points 1 day ago (1 children)

Doesn't avoiding JS typically structure a website in such a way that the browsers built-in assistive services can cover it easier?

[–] Vincent@feddit.nl 1 points 21 hours ago (1 children)

Not necessarily, unfortunately. (Though I guess technically it's easier to throw up barriers using JS, but it's not an inherent quality, and leaving it out doesn't automatically make it good.)

[–] xthexder@l.sw0.com 2 points 14 hours ago (1 children)

I'm curious what parts would be challenging to use with a screen reader? If a site just has basic links and no JS, I can't really think of anything unless the tab layout is somehow completely shuffled due CSS.

[–] Vincent@feddit.nl 1 points 2 hours ago

A comprehensive answer is out of scope and probably best given by a true accessibility specialist, but for example, if you only use <div> tags for everything, a lot of the screen reader's affordances for navigating are unusable. Images that carry information but not in their alt text are another simple example.

And then there are parts where JS could actively help. For example, if you have a tabbed interface, but clicking a tab results in a full page refresh, the screen reader loses all context.

Also keep in mind that there's more to assistive technology than just screen readers, e.g. sufficient colour contrast and keyboard navigability are important to many people. Too many websites still get those basics wrong.