Skip to content(if available)orjump to list(if available)

Accessibility and the Agentic Web

Accessibility and the Agentic Web

3 comments

·August 9, 2025
Visit

superkuh

An agent has nothing to process if there's no text on the page.

There are few things less accessible than web applications depending on bleeding edge javascript that might not get successfully executed. There are few things more accessible than text in an HTML web page on an HTML web site. If we really cared about accessibility for the differently abled we wouldn't be making such locked down, proprietary websites. But of course it's not really "we" doing this of our free will. It's corporations and their profit motives telling their human parts to make bad websites. And since that's where the money is in web dev it's become the default for all web devs and even shows up in institutional/government websites.

I don't think corps are going to change and I don't think something other than websites is the answer like the author suggests. We just need actual websites with web pages with text.

evertedsphere

> An agent has nothing to process if there's no text on the page

all of the major labs' flagship models are multimodal and the post is specifically about processing the non-text parts of the page

superkuh

A good point. I was unclear. I meant it in the sense that if the JS doesn't run fully successfully there won't be text, or images, or even source mark-up. Just some lists of remote JS CDN in source if anything. It'll mostly just be blank. Nothing for the multi-modal to do either.