We now require alternative text (from now to referred to as "alt text") to be added to all posts/comments containing media, such as images, animated GIFs, videos, audio files, and custom emojis.
EDIT: For files you share in the comments, a simple summary should be enough if they’re too complex.
We are committed to social equity and to reducing barriers of entry, including (digital) communication and culture. It takes each of us only a few moments to make a whole world of content (more) accessible to a bunch of folks.
When alt text is absent, a reminder will be issued. If you don't add the missing alt text within 48 hours, the post will be removed. No hard feelings.
If there are no clear and valid objections from the community, we will fully adopt the requirement in a week or so.
Draft for sidebar rule
We require alternative text (from now referred to as "alt text") to be added to all posts/comments containing media, such as images, animated GIFs, videos, audio files, and custom emojis.
We are committed to social equity and to reducing barriers of entry, including (digital) communication and culture. It takes each of us only a few moments to make a whole world of content (more) accessible to a bunch of folks.
When alt text is absent, a reminder will be issued. If you don't add the missing alt text within 48 hours, the post will be removed. No hard feelings.
Draft for guideline page in our wiki
(since the instance wiki is currently unusable, we were unable to expand the wiki accordingly; we will follow up on this when possible)
Guidelines for writing alternative text (from now referred to as "alt text")
For more details please feel free to take a look here:
Where to write it
Media posts
- For image posts (including animated ones) this can easily be done using the alt text field provided by Lemmy.
- For videos please provide these in the post's body.
Embeds (read: in post body or comments):
When embedding media in your posts or comments (regardless of media type) you can use markdown to add a label (aka. alt text).
- unlabelled embed:
- labelled embed:
How to write it
The following steps are there to establish a help framework/standard, but are not a hard requirement, especially since they aren't always applicable
General advice:
- Be descriptive, but concise
- Avoid extra phrases like "an image of" - the screen reader already knows the media type
- Summarize the purpose (alt text should convey the meaning or intent of the medium just as much as it describes the actual elements represented)
- Standard emoji are screen reader accessible and thus are allowed without descriptions
- Audio content must be transcribed if it does not already have a transcript or accessible subtitles
Additional guidelines, which we include because – if ignored – they make the job of screen readers harder or might make the output less useful for the people who utilise them
- Never add line breaks to alt text
- Never add the double quotes from whatever keyboard you use to alt text
- Don't write words in all-caps
- Avoid abbreviations like the plague if you can
- Don't type out emoticons
- Always end your sentences and your image descriptions with a full stop
Images:
- Write the main caption first (eg. the top/bottom text)
- Describe the background if essential
- Describe subjects in a logical order (iterate the following for each subject:)
- For subjects with a caption next to them, write the caption first
- Explain what the subject looks like and what it is doing
- Don't be afraid to give away the punchline when it would otherwise be hard to get
Animated Images/Videos:
- WRITE A CONTENT WARNING (if applicable): Be specific about what is in the content warning. In the context of flashing lights, it is recommended to use terms like "strobe lights", "flashing lights", "strobing", "seizure warning", or similar
- Use image steps where it makes sense
- Write a transcript of relevant on-screen text
- Write out all spoken audio, adding environmental sounds if they are important for understanding the video
- For videos you should provide an alt text that conveys the general context and a description where sensible.
-(E.g. if your video includes dialogue that is not reflected in subtitles, you are required to provide a transcript of it in the video description.)
I don't see how that reflects on the project, even more so since you are nor supporting them i any way by using SimpleX, since it's not paid, free/libre and decentralised
It's objectively one of the best secure messengers out there (eight next to Signal and Briar) with Matrix trailing by a bit but still faaaar ahead of most other stuff