RE: Survey about digital accessibility evaluation and monitoring practices

Having answered the OP's question, I'll take up the other comments. I think
the world has moved on from where it used to be. Probably two thirds of
websites use JavaScript now, often for quite important facilities of the
site, because of the clever things it can do. We can deplore the lack of
progressive enhancement, but there are too many developers out there that
just use JavaScript as standard who have no intention of adding extra
development time for that. Some stuff is very complex and would take hours
of extra work to create non-script alternatives. In the face of the numbers
I don't think we are going to change anything at this late stage. It would
be like trying to stop a river using a broom.

We can test for it when doing audits, but I'm sure that any company that's
invested in using a JavaScript library like Google's isn't going to buy
something else and rewrite their program just because we say it doesn't
work for text browsers. We could even ask Google to change theirs, but
there are thousands of JS libraries out there. I suspect, being realistic,
this is an insoluble problem. But this does leave a problem for
text-browser users.

There is another text browser, eLinks, that can run JavaScript. But I've
heard that it isn't very good at doing so, though I'm open to contradiction
on that if anyone here knows?