rich1.0npub1gcf8zwxgqpnl08gwnancjvvv0pggt5wgpphtjxpgrtzsz0tf6f6s4el3rhhttps://nostr.ae/npub1gcf8zwxgqpnl08gwnancjvvv0pggt5wgpphtjxpgrtzsz0tf6f6s4el3rhnjumphttps://nostr.aeI don't agree, but I respect the sentiment. Accessibility is extremely difficult to achieve, because accommodating those you literally cannot relate to takes a lot of energy. I would argue that learning to accommodate others takes exponentially more time and energy than creating a mockup, planning the code structure, and writing it combined. As someone who has some ADHD traits, sudden and subtle movements easily distract me, but unfortunately my curse is not something everyone can relate to, so it's hard for them to properly accommodate me when they don't even know if they're addressing it correctly. It's especially hard when the codebase typically becomes much more complex than it was to begin with. An anecdotal example, but one I think is relevant, is GNOME Calendar. Accessibility in Calendar is, to put it in the nicest way possible, almost nonexistent: Many widgets cannot be interacted with using a keyboard and can only be triggered using a pointer. I'd go so far as to say that it's literally unusable for anyone who absolutely relies on their keyboard. And believe me, I *want* to make it accessible. I *am* serious about it, but I have no idea where to start, and even the maintainer doesn't know what to do. Maybe GNOME Calendar is an ableist application because of this, I don't know, but I don't want to throw "ableist" around because many developers and maintainers don't even know what to do to accommodate those kinds of people. nostr:npub1jed589khcpur5du8w4e8xszypaq00r94qmk3x950a2lm3fx5lx6s3czzat nostr:npub1p095l6jcegr5j3zz0zjg2zukf7aq34awuetvkkpc8z78qwlvwavs5hm5vl