Welcome to Codidact Meta!
Codidact Meta is the "town hall" (meta-discussion site) for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Codidact warns me that images in a post lack alternative captions, yet no images exist.
When I attempt to update posts/294861/edit with:
Recently, I posted
electrical.codidact.com/comments/thread/11173#comment-27698, which cites two images from Wikipedia, and another from elsewhere.Although citing versioned MediaWiki URIs from Wikipedia isn't problematic, because they'll never become 404s, I've been forced to cite
szapphone.com/wp-content/uploads/2023/11/usb-c-pinout-diagram.webp, because I am unable to paste images into comments, which may well become so.
A workaround may exist: to post an image to an external hoster, [1] then embed that image with a CommonMark hyperlink ([2] it, regardless, wouldn't be convenient, nor significantly more stable.![]()). However, I've yet to ascertain whether that operates either, and
...I see:
<div class="notice is-warning"><ul><li>It looks like you're posting an image with no alt text. Alt text is important for accessibility. Consider adding alt text to the images in your post - <a href="/help/alt-text">read this help article</a> for details and help writing alt text.</li></ul></div>
However, that markup contains no embedded images:
Recently, I posted [`electrical.codidact.com/comments/thread/11173#comment-27698`](https://electrical.codidact.com/comments/thread/11173#comment-27698), which cites two images from Wikipedia, and another from elsewhere. Although citing versioned MediaWiki URIs from Wikipedia isn't problematic, because they'll never become 404s, I've been forced to cite [`szapphone.com/wp-content/uploads/2023/11/usb-c-pinout-diagram.webp`](https://www.szapphone.com/wp-content/uploads/2023/11/usb-c-pinout-diagram.webp), because I am unable to paste images into comments, which may well become so. <del>A workaround may exist: to post an image to an external hoster, [^1] then embed that image with a CommonMark hyperlink (`![]()`). However, I've yet to ascertain whether that operates either, and</del> [^2] it, regardless, wouldn't be convenient, nor *significantly* more stable. [^2]: [`comments/thread/11190#comment-27707`](https://meta.codidact.com/comments/thread/11190#comment-27707) [^1]: [`github.com/pixelfed/pixelfed/issues/6211#issue-3553892727`](https://github.com/pixelfed/pixelfed/issues/6211#issue-3553892727:~:text=I%20post%20almost%20solely%20unlisted%20images%2C%20to%20replace%20Imgur)
Very iconically, it even did so for this one, before I added the image [3] (and continues to with it added, despite its caption).
Current Triage Status
I have reported this upstream, at github.com/codidact/qpixel/issues/1889.
1 answer
I suspected that the bug was being triggered by the presence of the Markdown
`![]()`
even though this was enclosed in backticks.
When I tried posting the text up until the first horizontal line, the warning was not triggered, so it seemed that a code block (triple backticks) suppressed the warning, but inline code (single backticks) within a paragraph such as ![]() did not.
My guess was incorrect, because I did not receive the warning even after posting the text up until the second horizontal line.
It turns out that the parentheses need to be non-empty to trigger the warning:
The text inside the parentheses can be anything, including another parenthesis, which is why ![]()) triggers the warning but ![]() does not. Whether this is inside a code block or inline code is irrelevant.
One possible solution might be to omit code blocks and inline code from the post before applying the check.
0 comment threads
0 comment threads