News for hackers. Stuff that matters.

esphen

Re:Designing web page layouts for screen readers on Thursday December 27, 2018 @03:16PM (#18772259)
Be careful with this.

While it may sound like a good idea, it literally violates the U.S. Air Carrier Access Act and SAS (the airline) was recently fined for doing exactly what you describe[1].

This solution may also create a situation where the accessible website becomes a "second class citizen" in terms of content because managers are not willing to allocate resources to improving the dedicated accessibility-friendly version. I argue it's much better to make a11y a part of the specification process just like we did with the responsive web when we abandoned WAP.

[1]: https://www.transportation.gov/briefing-room/dot7418

Quite true. Thanks for the tip!
Yep, wscat is pretty a pretty nice tool! I used it as well, but it always bothered me that I couldn't tell it what to send to the server when running it. It's super handy to be able to file bugs with a one-liner to reproduce the bug.

That lead me to fork it and send a PR with that feature. It never got merged, so I simply created a new project, which ultimately lead to this :)

Holler if it works, that sounds pretty awesome!