If you think that's bad, try turning off JS in your browser, or even using not-Chromefox for a week. I use qutebrowser for what I consider an accessibility rea

If you think that's bad, try turning off JS in your browser, or even using not-Chromefox for a week. I use qutebrowser for what I consider an accessibility reason--not using a pointing device to prevent arm/shoulder pain. Keeping JS turned off improves performance on my older devices. For example, Slack tells me that my version of QB using Chromium 65.x for WebKit base, is unuspported. Oh well, good riddance. But that keeps me from accessing information about the hacker space I don't go to anymore because I can't find out if someone is there to let me in. This kind of arrogance about new device is widespread among hacker types who design and develop for Chrome latest on a top-spec machine and ignore everyone else. See also: Age simulation suit https://www.youtube.com/watch?v=vDUMIAfjBIc https://www.youtube.com/watch?v=vDUMIAfjBIc I tried just using wheelchair paths in NYC for a few weeks. Aside from only a small percentage of stations having any accomodations at all, most of the time the elevator to the platform is on the other end of the station from the elevator to the street. (Boston has almost stations accessible, with some lines having elevators in every station.) The Access-A-Ride service requires waiting several hours at times (I never used it, just witnessed it with other people.) TL;DR: If you're handicapped in NYC, don't schedule more than one appointment per day, and forget about doing anything else that day.