RE: Another question about use of aria-owns

+1 Jonathan.  

We do a little of both (extended ALT and narrative before image) in our Morbidity and Mortality Weekly Report - example at https://www.cdc.gov/mmwr/volumes/70/wr/mm7016a3.htm?s_cid=mm7016a3_w



Mark D. Urban
CDC/ATSDR Section 508 Accessibility Program Manager
Office of the Chief Information Officer (OCIO)
Office of the Chief Operating Officer (OCOO)
Murban@CDC.gov | 919-541-0562 office

-----Original Message-----
From: Jonathan Avila <jon.avila@levelaccess.com> 
Sent: Monday, April 26, 2021 10:14 PM
To: w3c-wai-ig@w3.org
Subject: RE: Another question about use of aria-owns

I'd highly recommend that long descriptions be available visually for users with low vision to be able to access.

Jonathan

-----Original Message-----
From: Jonathan Cohn <jonathan.cohn@cambiumassessment.com> 
Sent: Monday, April 26, 2021 5:40 PM
To: Jonathan Avila <jon.avila@levelaccess.com>
Cc: w3c-wai-ig@w3.org
Subject: Another question about use of aria-owns

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Hello,
I’m looking for a replacement for long description that could be navigated with a screen reader cursor but does not appear in the visible text like a figcaption does. It was suggested to use offscreen text immediately following the graphic (<img>) and then use an aria-details to point to the off screen text.
I’m wondering if perhaps using aria-owns in this situation might make sense, as that would more closely tie the full description to the <img> tag.
I will be trying this out over the next few days, but if there is an existing best practice that I should look at first?
Thanks!
Jonathan Cohn

Received on Wednesday, 28 April 2021 15:02:23 UTC