Post
@dgar love this. I’m 100% committed to accessibility. Both in my professional work and in personal spaces. It’s absolutely vital.
However, as you mentioned, not everyone understands how to make things accessible. Or even that they need to do things intentionally for this. Blocking someone for not knowing is a missed opportunity that is a disservice to people who need accommodations.
That’s why I wrote an article on hashtags. For awareness. That’s how we learn and do our best.
@ Mark Wyner Won’t Comply :vm: @ Dgar That's why I'm working on an entire wiki on how to describe images and write proper alt-texts in the Fediverse. Right now, it's planned to have over 40 pages, even though not even half of them are written yet. The topic is actually that complex, and there's so much that nobody on Mastodon knows when it comes to alt-text.
Besides, there isn't any image description guide otherwise that takes the non-Mastodon Fediverse in account. I'm going to cover that as well, although I won't add step-by-step guides on how to add an alt-text with this Web frontend or that mobile app. But I'm going to take into consideration that the non-Mastodon Fediverse is never limited to only 500 characters.
In case you're curious: Here is the link.
# Long # LongPost # CWLong # CWLongPost # FediMeta # FediverseMeta # CWFediMeta # CWFediverseMeta # CharacterLimit # CharacterLimits # CharacterLimitMeta # CWCharacterLimitMeta # AltText # AltTextMeta # CWAltTextMeta # ImageDescription # ImageDescriptions # ImageDescriptionMeta # CWImageDescriptionMeta # Wiki
@markwyner unpopular opinion probably but blocking someone for not using alt text is a cowardly way to handle this. Nobody will learn anything from it.
Your approach is so much better. Do you have a link to that article you wrote?
A space for Bonfire maintainers and contributors to communicate
