Long Reply
https://www.w3.org/WAI/WCAG22/Techniques/general/G92
This is among one of many techniques presented at the WCAG site you linked. You putting text in a top level comment would seem to me to satisfy this, at least in intent. If the image was removed, then a long description present on the page, even in a top level comment, would appropriately describe what was there. It also alleviates the searchability issue you highlighted. It also doesn't meet qualify under any failure criteria. Might be still only partially WCAG compliant but it would make it more accessible for users who need it.
You're right, I'm not an accessibility expert, only taken basic AODA training in Ontario. Even then, the training said to offer and make accomodations to the best extent possible. I do put transcripts on my text heavy image posts because the version of my Lemmy app I used at the time hadn't let me put alt text. Most of my inline images within the last year have the alt property filled. (example)
Unless you edit the post, demanding they fix it is the only solution.
Why is that the only solution to be more inclusive? That's not helping anyone. WCAG specifically advises against requiring it to be done using their specifically defined techniques only, just that the outcome is an appropriately accessible piece for people who need it. Try this if you want to implore to edit it or do it in the future:
To help with WCAG accessibility, OP please put a transcript on this image! I've made one for you... [Transcript].
It took me less than two minutes to put up the transcript in my previous reply.
addendum: It does mention to be a programmatically determinable non-text alternative, it must be from author-supplied data that links to it, to specifically be conformant to this standard. You can still put in the minimal effort to take the author's data and link it for the people who can't so that users with assisstive technologies can easily find it on the same page when they go looking. Like I said, complain and be part of the solution to make things more accessible for people who need it. I hadn't claimed that adding one would magically make it fully WCAG 2.2 complaint, only in that direction.