- From: Maciej Stachowiak <mjs@apple.com>
- Date: Wed, 19 Sep 2012 02:09:35 -0700
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, "public-html-a11y@w3.org Task Force" <public-html-a11y@w3.org>
On Sep 19, 2012, at 2:01 AM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote: > Maciej Stachowiak, Wed, 19 Sep 2012 01:46:24 -0700: >> >> On Sep 19, 2012, at 1:13 AM, Benjamin Hawkes-Lewis >> <bhawkeslewis@googlemail.com> wrote: >> >>> On Wed, Sep 19, 2012 at 8:29 AM, Maciej Stachowiak <mjs@apple.com> wrote: >>>> I'm not claiming it's not implementable. Just justifying the point >>>> that these encouragements are more than just suggestions. >>> >>> Note the same section of the spec: >>> >>> http://dev.w3.org/html5/spec/rendering.html#links,-forms,-and-navigation >>> >>> contains this expectation: >>> >>> "User agents are expected to allow users to navigate browsing contexts >>> to the resources indicated by the cite attributes on q, blockquote, >>> ins, and del elements." >>> >>> Would you agree the proposed "longdesc" expectation seems within the >>> same order of magnitude in terms of likely implementation outcomes? >> >> Yes. >> >> I hadn't noticed this before, so I filed >> <https://www.w3.org/Bugs/Public/show_bug.cgi?id=18915>. > > But you don't propose to obsolete @cite in the same go? To propose such a change, I'd need to understand whether data mining tools such as search engines make any effective use of it to comment usefully on whether it should exist for non-browser purposes. I've heard that they do. Verifying this claim is more work than testing browsers, unfortunately. > If so, could you accept a non-obsolete @longdesc without the > "expected/must" level? I'm not expressing a position on that question (or the document conformance status of @cite) at this time. Regards, Maciej
Received on Wednesday, 19 September 2012 09:10:06 UTC