Toot by Matt CampbellMatt Campbell (toot.cafe)

@objectinspace @tristan I absolutely simpathize with Drew here. He just wants to get shit done. And honestly this whole conversation about how can we make it accessible without developers having to give a damn is a dead end. It's like asking "How can we make this pretty and solve problems wi thout designers having to give a damn." Neither of these things are going to happen, except designers do give a damn about making it pretty at least, if for no other reason than their clients give a damn. So at the end of the day people have to give a damn about accessibility other than people with disabilities or we're not getting accessibility. And I absolutely don't blame Drew for being pissed off that Proton doesn't seem to give a damn.

Toot by TerryBTerryB (babka.social)

@ppatel @SteveSawczyn I t hink Pratik is probably so used to looking for meatless options that he just completely missed the meat ones. And to be fair, the bacon/ham/steak options are sort of sprinked in, at least from a screen reader user point of view, and so don't make up the main part of the offerings. It's sort of how vegetarian or vegan options get treated in the US, except in reverse.

Toot by Matt CampbellMatt Campbell (toot.cafe)

@tristan @objectinspace Requiring each user interface designer to directly put effort into making their interface beautiful and useable doesn't scale either, and yet it somehow still happens. I'm all for making it easier for developers and designers to make their apps/web things accessible, just like I'm all in on making it easier for content creators to make their content accessible. But I don't think it's unreasonable to ask developers or even content creators to put effort into accessibility when they put effort into a ton of other things, and I don't believe it's any more possible to automate or even automatize accessibility any more than it is to automate or automatize security.