summaryrefslogtreecommitdiffstats
path: root/content/notebook/archive/in-depth-image-descriptions.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/notebook/archive/in-depth-image-descriptions.md')
-rw-r--r--content/notebook/archive/in-depth-image-descriptions.md31
1 files changed, 31 insertions, 0 deletions
diff --git a/content/notebook/archive/in-depth-image-descriptions.md b/content/notebook/archive/in-depth-image-descriptions.md
new file mode 100644
index 0000000..3143a36
--- /dev/null
+++ b/content/notebook/archive/in-depth-image-descriptions.md
@@ -0,0 +1,31 @@
1---
2schema_type: DigitalDocument
3title: Detailed Image Descriptions Aren't Always Helpful
4date: 2022-05-05
5
6references:
7 - label: Original Post
8 url: https://mk.vulpes.one/notes/8zwxp9lywc
9---
10
11::: alert
12I noticed that quite a few people write very extensive image descriptions.
13Mastodon in particular implies that this is the correct way since the character limit for them is [three times as high as the limit for the actual post content](https://github.com/mastodon/mastodon/pull/11819).
14However, there are common situations where these image descriptions are in fact not helpful.
15:::
16
17Imagine you're using an online shop.
18What you'll typically see is a list of products where each list item has a small preview image, a product name and some other metadata.\
19Now imagine that the shop displays a long textual description for each product instead.
20This is what the timeline appears like to screen reader users if long image descriptions are used.
21And unlike people seeing the text, they don't have the luxury of skimming to grasp vital information quickly -- they can only wait for the screen reader to read all of it or until they decide to skip the rest.
22
23Detailed descriptions are only helpful when the user has decided the content is interesting to them.
24Currently, most fedi frontends put them in the attachment's `alt` attribute, which is fine if the user is currently viewing a single post instead of the timeline.
25But on the timeline, it's much more important to have quick summaries instead.\
26In terms of the example above, it's the same when viewing a single product vs. the product list.
27You're only interested in the details if a product is interesting to you.
28
29Image description on fedi are a step up from having none at all, but they're still inadequate.
30Ideally, you could provide both a quick summary and an in-depth description, and the UI presents both in a way that's the most helpful.\
31Since this possibility doesn't exist, please consider keeping image descriptions short and putting the long description in the post body.