Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Comments on Add an explicit Markdown syntax for decorative images

Parent

Add an explicit Markdown syntax for decorative images

+4
−3

When uploading an image on a Codidact community, users are prompted to add alt text - a text alternative to an image - for that image. If they go to submit a post without doing so, or when submitting a post with blank alt text, they are reminded with a link to the help center page on alt text.

However, in certain cases, particularly for decorative images, blank alt text is the correct approach. The problem is that whether or not it's appropriate in a particular case is not something that can be detected programmatically, and so users who are correctly setting a decorative image to have blank alt text will still be prompted to set alt text for the image (although it will not prevent the post from being submitted with the default or blank alt text).

To make it clearer to the system and to any potential editors, though, I'd like to propose an explicit Markdown syntax for decorative images, which can then be served with blank alt text by the system.

This should be something like ![!decorative](image URL) - something unlikely to be used unintentionally and that makes it clear to both the system and human editors that this is an intentional usage of this syntax. The system then knows to serve this image with the alt attribute set to alt="".

Is something along these lines possible to add to the Markdown handling for QPixel?

History

2 comment threads

Where do you expect decorative images to be used here? (1 comment)
What's a "decorative" image? (3 comments)
Post
+0
−4

There is already too much nanny-ware in the world, Codidact shouldn't be adding to it.

Whether an author includes alt-text for images, whether that alt-text is meaningful, or whether it is appropriate or unnecessary for a particular image is for the author to decide. This is not different from using proper grammar, spelling, and punctuation. The system shouldn't be interfering with author agency, style, and what information is presented.

Of course posts will be judged by all the other users, in part on quality items like grammar, spelling, punctuation, overall formatting, and the like. If you feel a post is badly written, then a downvote can be appropriate. If an image in a post didn't have alt-text but you feel strongly it should have, that's a legitimate reason for a downvote (hopefully with an explanatory comment).

In short, only the human users should be judging posts and dealing with them accordingly. Automated systems shouldn't be trying to make such judgement calls. Not only is it really annoying, but as your question points out, such systems don't have enough information to do the job right.

History

1 comment thread

I don't see a dismissable reminder as removing author agency (3 comments)
I don't see a dismissable reminder as removing author agency
trichoplax‭ wrote 9 months ago

I would agree that the system should not override an author's choices, but the current system provides a reminder (which I often find helpful) and the question proposes a way of helping future readers of the raw Markdown understand the author's original intentions. This seems to support author agency rather than override it.

It's important to me that the reminder be dismissable, but I wouldn't want it to be removed, except possibly to make it opt out for users who are confident they will never need reminding. For me personally, my posts are higher quality than they would have been without the reminders.

Olin Lathrop‭ wrote 9 months ago

I find any such "reminders" to be very annoying nagware. If people actually want this reminder, then it should be optional and opt-in.

The current system second-guesses author intent. While that doesn't outright dictate its own policy, it does reduce author freedom by adding hassle to writing a post the way you think it should be.

Olin Lathrop‭, I believe that ensuring that all authors are less likely to forget to consider the optically incapable is worth such minor annoyance.