Summary guideline for the alt attribute:
For more decent guidelines on good
alt attribute authoring, see:
Exception: sometimes the WHATWG spec has bad or bad out-of-context advice, e.g.
"...the alt attribute's value should never contain text that could be considered the image's caption, title, or legend."
This is poor advice because:
- Using the phrase should never is "scare" advice (more likely to cause inaction than action)
- More likely to result in empty alt attributes than anything useful
- An empty string "" contains no "text that could be considered the image's caption, title, or legend", satisfies the WHATWG statement, yet adds little or no value.
Instead, see the summary guideline for positive guidance. In particular for this case:
Alt text on images in a post can cause issues when trying to display that post in a reader.
On adactio.com, the img alt text is the same as the post contents. Since alt text is included in the p-name parsed result, this results in duplicated text for the posts.
Below is a screenshot showing a few recent posts from adactio.com as rendered in an IRC-based reader.
Below are two posts from tantek.com in the same reader. Note that the text of the first post includes "a jpg" which is the alt text of the image.
Currently the python mf2 parser does not include alt text in the parsed result, so these posts look fine in Woodwind. However, if it did, as the parsing algorithm suggests, this is how a post would look. (with more representative alt text)
Woodwind has no way of knowing the first line of the name property came from the alt text.