this post was submitted on 05 May 2025
102 points (95.5% liked)
Programming
20020 readers
140 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
view the rest of the comments
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.)
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.
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.
Thanks for responding. I'm not really a web dev, so I haven't thought about it much.
The tab layout and
<div>examples were definitely not things I was thinking about. I guess that's a good incentive to use tags like<section>and<article>instead of divs with CSS classes.I'm actually a bit color blind myself, so I appreciate sites being high contrast and not relying on color alone for indicators. A surprising number of sites completely break when trying to zoom in and make text bigger too, which is often due to bad floating layouts. Especially if it's resized with JS...