-

A person applies clown makeup in four panels, each showing a step in their transformation. The plain background keeps the focus on the person, who expresses growing resignation. Each panel is captioned: Panel 1: "Maybe if I work hard" Panel 2: <br />"Go above and beyond" Panel 3: "Never use sick or vacation days" Panel 4: "The company will notice And appdeciate" The meme visually highlights a progression from hope to disillusionment, using the clown makeup as a metaphor <br />for self-deprecation and misplaced optimism.

2025-05-30 02:55:22

Erik L. Midtsveen 🏴🏳️‍⚧️🇵🇸

midtsveen@social.linux.pizza

#WorkingClass #Wages #Capitalism #Socialism #Anarchy #Meme #Memes #Humor

2025-05-30 02:59:27

Erik L. Midtsveen 🏴🏳️‍⚧️🇵🇸

midtsveen@social.linux.pizza

I noticed some mistakes in my alt text and have fixed them to improve accessibility for everyone, including people with disabilities.

If you find any issues with my alt text, please feel free to let me know, I want to make sure it works well for you. Thank you!

#Disability #Disabled #AltText #Blind

2025-06-01 10:07:46

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@Erik L. Midtsveen 🏳️‍⚧️🇳🇴 If you really want some criticism:

Alt-text really should not contain line breaks, nor should it contain the quotations marks on your keyboard. Neither are standard alt-text elements. And just because Mastodon renders them with no problems, doesn't mean everything does. Not even in the Fediverse.

As for line breaks: Some screen readers will take each new line for a whole new alt-text and therefore a whole new image. And they will read multi-line alt-texts as alt-texts of multiple images, e.g. starting each line with, "Graphic." This has been pointed out by Steve Faulkner in 2015.

As for quotation marks: For one, just like line breaks, they're actually completely useless for the actual target audience of alt-text, namely blind or visually-impaired people. Screen readers don't read out quotation marks. I mean, how should they?

But if a frontend doesn't render quotation marks properly, screen readers will read out gobbledygook where there's a quotation mark because they will see gobbledygook in the place of that quotation mark, because the frontend renders quotation marks as gobbledygook.

For example, there's Hubzilla which is what I'm posting from right now, so it's very much part of the Fediverse. Hubzilla renders quotation marks in alt-text as their HTML entities, namely &⁠quot;. A screen reader will read out every single quotation mark as, "And quot."

And then there are two descendants of Hubzilla made by Hubzilla's own creator, (streams) and Forte. The same quotation marks that you have on whatever keyboard you use, they use as alt-text delimiters. When the first quotation mark comes, they think it's the end of the alt-text, and they stop parsing and rendering the alt-text. For them, your alt-text ends right after, "Panel 1:"

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #AltText #AltTextMeta #CWAltTextMeta