

Enforce web accessibility.
Bluesky and other parts of the fediverse like mastodon do this well.
Some communities do it better, but lemmy instances overall do not.
Lemmy users consistently show they do not get it, defend panaceas that do not fulfill web accessibility, and respond with hostility when it’s pointed out that inaccessible content is a systematic failure of will (poor choices of client & execution), not of capacity.

In particular, the
altattribute has existed since HTML 1.2 draft in 1993 (same year as initial release of HTML) when text-based web browsers (which still exist) were common. The web was accessible since the beginning.This reinforces the earlier point that web accessibility is not a limitation of capacity, but of will. The threadiverse is lagging.
That can be enforced & promoted in the environment. Platforms that do this better even in the fediverse were mentioned.
It’s basic markdown.
As WebAIM states
a text alternative is a substitute that conveys equivalent purpose in context. Unless AI reads an author’s mind, it will miss contextual meaning & intent. It will also garble text, misinterpret non-text content, sequence complex content wrong.
The
altattribute in particular is typically accurate & equivalent, succinct, not redundant. Complex images get a succinctaltattribute and an adjacent text alternative or link to text alternative.Of course, an image of text doesn’t need to be an image at all. Culture & enforcement could discourage that anti-pattern.
For the threadiverse, the top issue is images lacking text alternative. However, text alternatives apply to any non-text content[1] and web accessibility encompasses more than that, which the platform mostly addresses.
the formal guideline:
↩︎