In the 15 days prior to the new site launch, @ravelry tweeted 11 times (not including any replies). In the almost 15 days since, they have tweeted twice. Neither addressed the fact that they are endangering lives. They have ignored the fact that people could die.

There is one and only one appropriate response to your work endangering users - revert to a safe version until the new version can be fixed. Not leave up the dangerous version until the calls for change die down. @ravelry #RavelryAccessibility #RavelryIsDangerous #accessibility

And no, @ravelry - putting an option for a skin of the old version is not the same as reverting. 1 - I have to access the dangerous version to reach the safe one. 2 - It& #39;s not the actual old version, which means it doesn& #39;t load before the new version at times, again forcing users

to view the dangerous version. Everyone knows skins don& #39;t always load faster than the base site. It took seconds to cause me and others harm, your "fix" is too late for that. When a product causes harm it& #39;s recalled, not given a new paint job.

Reverting to a safe version of a website is LITERALLY one of the fastest and easiest fixes to a product mistake. It& #39;s a zero-cost fix. It might suck to have to wait longer for launch and retool the site, but it& #39;s harmless for you. Does @ravelry literally not care what happens??