W3C home > Mailing lists > Public > public-digipub-ig@w3.org > November 2015

RE: FW: Proposal: remove aria-describedat from the ARIA 1.1 specification

From: Gunderson, Jon R <jongund@illinois.edu>
Date: Fri, 13 Nov 2015 14:49:48 +0000
To: "Schnabel, Stefan" <stefan.schnabel@sap.com>, Steve Faulkner <faulkner.steve@gmail.com>, Chaals McCathie Nevile <chaals@yandex-team.ru>
CC: Janina Sajka <janina@rednote.net>, Shane McCarron <shane@aptest.com>, W3C WAI Protocols & Formats <public-pfwg@w3.org>, "public-digipub-ig@w3.org" <public-digipub-ig@w3.org>
Message-ID: <46739F12637CC94E82F75FF874E4A1473B7DA944@CITESMBX6.ad.uillinois.edu>
Stefan,

Any content, it would behave similar to DETAILS/SUMMARY elements, so they can’t say they don’t know how to do it.

Jon

From: Schnabel, Stefan [mailto:stefan.schnabel@sap.com]
Sent: Friday, November 13, 2015 8:48 AM
To: Gunderson, Jon R <jongund@illinois.edu>; Steve Faulkner <faulkner.steve@gmail.com>; Chaals McCathie Nevile <chaals@yandex-team.ru>
Cc: Janina Sajka <janina@rednote.net>; Shane McCarron <shane@aptest.com>; W3C WAI Protocols & Formats <public-pfwg@w3.org>; public-digipub-ig@w3.org
Subject: RE: FW: Proposal: remove aria-describedat from the ARIA 1.1 specification

Jon,

What kind of content will be allowed and which one not? Only text nodes?


-        Stefan

From: Gunderson, Jon R [mailto:jongund@illinois.edu]
Sent: Freitag, 13. November 2015 15:42
To: Steve Faulkner; Chaals McCathie Nevile
Cc: Janina Sajka; Shane McCarron; W3C WAI Protocols & Formats; public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>
Subject: RE: FW: Proposal: remove aria-describedat from the ARIA 1.1 specification

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]
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=>
Received on Friday, 13 November 2015 14:51:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 25 April 2017 10:44:35 UTC