JosieAccessibility is not an afterthought for software engineering. It should be incorporated in the design process for your system.
The more as software engineers we understand that things like accessibility and testing are crucial to a successful application, the less we are alienating people from using our platform.
Mastodon’s blatant disregard for basic UX practices and overall UI design is not a learning curve; It’s a poorly constructed gate.
This is a good resource:
So is @[email protected]’s Testing Accessibility course.
These are not the only resources, but I highly suggest every SWE take an accessibility course. All of my companies had us take them at least once a year because ADA non-compliance fines are not a joke.
One last thing:
YOUR APP DOESN’T MATTER IF EVERYONE CAN’T USE IT.
DawnRay ammonI have no issues with it , maybe it is just you?
Brian C KelleyMoaning and groaning for 3 days is also not a learning curve. Don't like it? fix it:
https://github.com/mastodon/mastodon
Took me 10 seconds on google to find other people to talk about accessibility with:
https://yatil.net/blog/accessibility-in-the-fediverse-and-mastodon
Be part of the signal, not the noise. Right now you're only part of the noise.
Amelia@javavvitch This.
If disabled voices aren't being actively heard in the development conversation, the product will be, inevitably, less accessible - and in practice, this means it will be effectively exclusionary.
I would also take the call one step further: as long as disabled voices still aren't leading development conversations, we continue leaving tremendous potential for improvement unrealized.