Re: Proposal: remove aria-describedat from the ARIA 1.1 specification

This issue for extended external descriptions is not only an issue for Images, but will be used on any web element potentially (tables for a simple example).

_______________________________

Charles LaPierre
charlesl@benetech.org




> On Nov 13, 2015, at 6:42 AM, Gunderson, Jon R <jongund@illinois.edu> wrote:
> 
> Charles and Steve,
> 
> If we want native semantics let’s ask the HTML5 working group to modify the IMG element to allow the IMG element to act like SUMMARY/DETAILS elements.
> 
> If an IMG element can be a container for other content (e.g. including iframes to shared long descriptions) then the markup becomes much simpler and testable by evaluation tools.  All this talk about creating links and flowto’s is going to be very prone to errors and just plain being overlooked.
> 
> If the IMG element contains content it would get the same “twisty” the SUMMARY/DETAILS elements get if the IMG element contains any content.
> 
> <img scr=”my-imag.png” alt=”short description of image”>
>   Long description of image ….  Including tables and iframes
> </img>
> 
> This approach makes it easier for everyone, but especially authors.
> 
> Jon
> 
> 
> From: Steve Faulkner [mailto:faulkner.steve@gmail.com <mailto:faulkner.steve@gmail.com>]
> Sent: Friday, November 13, 2015 4:35 AM
> To: Chaals McCathie Nevile <chaals@yandex-team.ru <mailto:chaals@yandex-team.ru>>
> Cc: Janina Sajka <janina@rednote.net <mailto:janina@rednote.net>>; Shane McCarron <shane@aptest.com <mailto:shane@aptest.com>>; W3C WAI Protocols & Formats <public-pfwg@w3.org <mailto:public-pfwg@w3.org>>; public-digipub-ig@w3.org <mailto:public-digipub-ig@w3.org>
> Subject: Re: FW: Proposal: remove aria-describedat from the ARIA 1.1 specification
> 
> 
> On 13 November 2015 at 10:32, Chaals McCathie Nevile <chaals@yandex-team.ru <mailto:chaals@yandex-team.ru>> wrote:
> Also, why not use a pair of HTML links, which provide bidirectional relationships for the Web and work for all users?
> 
> I couldn't agree more, we should be using standard HTML, which works for all users, wherhever we can.
> 
> --
> 
> Regards
> 
> SteveF
> Current Standards Work @W3C <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paciellogroup.com_blog_2015_03_current-2Dstandards-2Dwork-2Dat-2Dw3c_&d=BQMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=h7YJ6Ekq0h4M1G-8RA-K98XEPpvoE1buAMtd47JmLZM&s=u9SoScJoeoteFShYONm0Wv0nTaYGCwBrmhN0zjx5Crk&e=>