Re:Google.com search now refusing to search for FF esr 128 w...
by inetknght on Wednesday January 15, 2025 @09:29PM
(#42720308)
That doesn't make it a myth. There are plenty of screen readers that break directly because of shitty use of javascript.
Re:Google.com search now refusing to search for FF esr 128 w...
by duskwuff on Wednesday January 15, 2025 @10:56PM
(#42720994)
Sure. But it certainly isn't as simple as "screen readers don't support Javascript or CSS" (or whatever). You can make an inaccessible web site with or without modern web technologies - a site based around HTML image maps or table layouts will baffle a screen reader just as badly.
Re:Google.com search now refusing to search for FF esr 128 w...
by throwaway290 on Wednesday January 15, 2025 @09:43PM
(#42720414)
Yep. There's a bazillion of accessible JS libraries. Just manage tabindex/aria attributes. Accessibility is about actual DOM not the html string returned from server.
JS gives the same improvements for screen readers as for everyone else especially with complex apps.
Bad JS of course ruins things as usual, same bad HTML with table layout or whatever. But that's not JS on google.com;)
Screen readers are not a type of web browser. They are software which interacts with other software running on the computer, including web browsers. There is nothing which inherently makes JS or CSS incompatible with screen readers.