this post was submitted on 05 May 2025
107 points (95.7% liked)

Programming

21432 readers
313 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
[–] Vincent 36 points 2 months ago* (last edited 2 months ago) (14 children)

Note there's a group of users that larger than the group of users without JS (for whatever reason): users of assistive technology. And they don't even have a choice.

While I'm all for considering the needs of every user... If you get to the point where you're worrying about no-JS users, I hope you've already considered the needs of people with disabilities, whether temporary or permanent.

Edit: oh right, wanted to add: just making a site work without JS doesn't automatically make it accessible to people with special needs.

[–] wewbull@feddit.uk 0 points 2 months ago (1 children)

They overlap. Js is a shit technology for the blind.

Dynamic sites that move / hide / unhide components as you do things are unhelpful and confusing. A screen reader will tell you what's under the cursor right now. If that changes, you don't get notified that you're now pointing at something else.

Static sites are better for accessibility too.

[–] Vincent 1 points 2 months ago

They can overlap, yes. Static sites are definitely not automatically better for accessibility.

load more comments (12 replies)