Re: Return of the londesc conundrum

Like Léonie, I recommend the DETAILS/SUMMARY tag solution. Penn State has an example on their accessibility web site.

https://accessibility.psu.edu/images/imageshtml/#extended


The screen reader users who have tested this really like how it functions. They also like that they can skip if they don't think it's relevant.

Another benefit of this solution over longdesc is that it's available to ALL users. With complex graphics, I think text descriptions help more users beyond those using a screen reader.  An example I use are navigation instructions - some sighted users prefer a map, but others need the instructions in a text list.

 It also has other good functions such as allowing to post audio transcriptions or other long annotations. And It doesn't require extra scripting to make it keyboard accessible.

Hope this helps.

Best
Elizabeth


On Jan 14, 2022, at 9:48 AM, Léonie Watson <lwatson@tetralogical.com<mailto:lwatson@tetralogical.com>> wrote:

For images that are not part of graphical links, the solution I like is to use a details/summary component (or custom equivalent), like this:


<details>

<summary><img src="image.png alt="Short text description here"></details>


<p>Longer description here...</p>

</details>


Léonie.


On 14/01/2022 14:28, Jonathan Cohn wrote:
What is the suggested pattern for providing additional information about a graphic at this time? Is it Figure with fig figcaption? I would think this not ideal for more explicit descriptions of graphics. Or perhaps a link surrounding the omg often used to bring up a full size image should also have text about the image.
Thanks!
Jonathan Cohn

On Jan 14, 2022, at 7:17 AM, Léonie Watson <lwatson@tetralogical.com<mailto:lwatson@tetralogical.com>> wrote:

There is almost no support for longdesc in browsers or by screen readers anymore. I haven't checked since June last year, but the results at that time are documented here:

https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftest-cases.tink.uk%2Flongdesc%2Findex.html&amp;data=04%7C01%7Cejp10%40psu.edu%7Ccecd90a6e47e46dba6b308d9d76d7eac%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637777687546962876%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=%2FRpOJf8Qxn12Q3NE2VwGDBTh8s%2FC58WwDrv%2FNOLQBQg%3D&amp;reserved=0



Léonie.

On 14/01/2022 07:02, Stephane Deschamps wrote:
Hello fellow accessibility people,

I remember the age-long battle to keep longdesc into the spec, and then moving it to its own[1] as the main spec marked it as deprecated. It is now marked as **obsolete and non-conforming** in the HTML5.2 spec[2] so I'm at a loss as to whether one can implement it or not, considering one official recommendation versus the other.

Could anyone clear that up for me please?

Thanks for any input!
Stephane

[1] https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fhtml-longdesc%2F&amp;data=04%7C01%7Cejp10%40psu.edu%7Ccecd90a6e47e46dba6b308d9d76d7eac%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637777687546962876%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=vsOElubRyxyIRXZAVXjw3T8FqsKifsxAE9QX5ovNY0M%3D&amp;reserved=0

[2] https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhtml.spec.whatwg.org%2Fmultipage%2Fobsolete.html%23non-conforming-features&amp;data=04%7C01%7Cejp10%40psu.edu%7Ccecd90a6e47e46dba6b308d9d76d7eac%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637777687546962876%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=mxV%2FEs%2F9mHm6Pr1uwgd8vRBjUwGfKGVn520wjaC3Pf0%3D&amp;reserved=0


--
Director @TetraLogical
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftetralogical.com%2F&amp;data=04%7C01%7Cejp10%40psu.edu%7Ccecd90a6e47e46dba6b308d9d76d7eac%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637777687546962876%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=6fuuTA%2BJ%2FBExk3nPrC8fxO4j5XDiyAj10CR69OMANPU%3D&amp;reserved=0



--
Director @TetraLogical
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftetralogical.com%2F&amp;data=04%7C01%7Cejp10%40psu.edu%7Ccecd90a6e47e46dba6b308d9d76d7eac%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637777687546962876%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=6fuuTA%2BJ%2FBExk3nPrC8fxO4j5XDiyAj10CR69OMANPU%3D&amp;reserved=0




=-=-=-=-=-=-=-=-=-=-=-=-=
Elizabeth J. Pyatt, Ph.D.
Accessibility IT Consultant
IT Accessibility
Office of the Deputy CIO
accessibility@psu.edu<mailto:accessibility@psu.edu> (General accessibility questions)
ejp10@psu.edu<mailto:ejp10@psu.edu>

25 Shields Building
University Park, PA 16802
https://accessibility.psu.edu