Long descriptions for generated shapes/graphs etc.

[oucnelson]

Hello,

I am passing on a request from Maths colleagues from The Open University (UK).

They would like a collapsible long description widget where they can surface generated descriptions for generated shapes/graphs etc.

As they say a picture is worth a thousand words, here are some mockups of what the collapsible button could look like as a starter for ten (screenshots based on OU Moodle theme):

I don't seem able to attach an example STACK question, but it allows me to attach a zip, so here is a zipped STACK question!
questions-MST368-24J-adjmatrix A2-20240430-1403.zip
In this question, my colleagues were trying to place the generated description into our transcript filter (which doesn't work because our filters don't get called in the way they've tried to use them). Our transcript filter is a collapsible widget, and then they asked me when it didn't work!

Therefore, please could we have a collapsible long description widget that we can place in the question text and call generated descriptions for generated assets.

Many thanks in advance.

[christianp]

(I'm not a STACK person but this is within my area of expertise)
If you can, use the standard <details> tag

[oucnelson]

@christianp Thanks for that tip - I wasn't aware of that tag(!). I don't think it quite fully does what my colleagues want, but I've passed it along and will update this ticket if so.

[sangwinc]

Thanks @christianp, I agree the

tag is probably what we will choose to use to render the long description. However, it would make sense to have a consistent mechanism for tagging the information as such. So, some kind of a [[longdescription]]...[[/longdescription]] block associated with an image would enable our bulk checker to identify images without this accessibility feature would be sensible.

[hayden-MB]

Hello @oucnelson! Could I ask what features you would have for this block in an ideal word which the html details option, or the [[hint]] block with an alternative title, does not provide? If we are designing this feature we don't want to be focusing on the wrong aspect of the request.