Tamas G@tristan @objectinspace @matt Why should you actually fix it when the four freedoms can become the four responsibilities for a statistically insignificant subset of your users? And by "subset of users" I mean the users who will actually speak up about accessibility of FLOSS, which isn't that many.
@acarson @tristan @objectinspace @matt Fair enough yeah, but I think the bigger issue is that those smaller “subset” of users have to be more technically skilled or aware to detailed ways in which their favorite application fails them and may need fixing, when we consider only the area of user experience impact or general un-usability, something that someone who can see / use all senses may not need to do or worry on knowing specifics about.
@Tamasg @tristan @objectinspace @matt Yeah which makes your group smaller, and also, isn’t how any of this is supposed to work. They’re basically telling people “You have to be hackers in order to even have a shot at fixing things that are mission critical, and that’s not even a promise that we’re actually going to accept the fix”.
@acarson @tristan @objectinspace @matt not the first Open-source project area I’ve seen that attitude. Right now trusting a non-experienced developer (and by that I mean someone who never learned any practices for making accessible code for their specialty) is about as good as trusting Chat GPT for accessibility advice, in that neither will know which labeling, navigation, interaction technique works best for that control or group of them.