diff options
| -rw-r--r-- | docs/random/xkcdbot.md | 57 |
1 files changed, 57 insertions, 0 deletions
diff --git a/docs/random/xkcdbot.md b/docs/random/xkcdbot.md index 47ea2c0..7b5735f 100644 --- a/docs/random/xkcdbot.md +++ b/docs/random/xkcdbot.md @@ -1,5 +1,9 @@ # xkcdbot +First version 2022-11-29 + +Updated 2023-10-22 +  @@ -66,3 +70,56 @@ comic. I believe this resolves all remaining questions on this topic. No further research is needed. + +## Update (2023-10-22) + +It turns out this does not resolve all remaining questions on this topic, +and further research is needed. + +The problem is accessibility. On xkcd.com, if you hover your mouse on the +comic, a tooltip shows up. This is known as "hover text" or "title text", +which uses the "title" HTML attribute. In 2019 I wanted to create +a similar experience, so I put it in the alt text. + +However it wasn't the intended purpose. The alt text is meant for: + +- A replacement when the image cannot be displayed +- Assistive technology such as screen readers + +On the fediverse it's mostly the latter. Right now, the awesome [Sam +Levine](https://botsin.space/@SRLevine@urbanists.social) is doing the +noble work of replying to every post with a captioned version of the same +comic. + +But it is a workaround. Around my reluctance to touch my rotten codebase, +my incompetence as a developer, and my lack of interest to caption the +comics myself. Whenever I post on my main handle, I make sure to caption +my images and audio. But sadly xkcdbot cannot do that right now. + +> Why not? + +Because Randall doesn't caption comics when they are posted. + +> Can't you fetch the caption from explainxkcd? + +That might take hours before it's ready. Plus, caption might be incomplete +and susceptible to vandals. + +> Just delay the post until the caption is ready! + +We don't know how long it will take. Also, I created the bot in order to +read xkcd as soon as possible. I cannot accept the delay. + +> Just edit the post! + +I made the bot in 2019, when "edit" wasn't a thing. I _could_ make this +feature right now, but I haven't touched my codebase for 4 years, and +I don't use Node.js anymore. + +## Conclusion + +Accessibility for a bot is not an easy task. It's not a tech problem; it's +a matter of community. I admit I cannot solve it by myself. Therefore, +I am going to ask for the community for help. + +To be continued. |