- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Wed, 4 May 2011 15:36:22 +0200
- To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Cc: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Laura Carlson <laura.lee.carlson@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Benjamin Hawkes-Lewis, Wed, 4 May 2011 14:17:07 +0100: > On Wed, May 4, 2011 at 12:20 PM, Leif Halvard Silli: >> May be a list of acceptable formats should be given rather than >> 'structured host language content'. > > What list? http://www.w3.org/mid/20110504144508806890.f1e4453a@xn--mlform-iua.no >>> Note that if we impose such a constraint we will render some existing >>> longdesc use non-conforming. Three of Laura's examples of @longdesc >>> in the wild use plain text for long descriptions. >>> >>> http://www.d.umn.edu/~lcarlson/research/ld.html#fakoo >>> http://www.d.umn.edu/~lcarlson/research/ld.html#securian >>> http://www.d.umn.edu/~lcarlson/research/ld.html#buffalo >> >> HTML5 is not about blessing existing content. > > I didn't say it was. Do we have any reason to say the above should be > non-conforming though? Is it inaccessible? http://www.w3.org/mid/20110504144508806890.f1e4453a@xn--mlform-iua.no .... >> Purpose of longdesc is structured content. We undermine its legitimacy, >> IMHO, if we water it out. > > The purpose of @longdesc in the suggestex text is twofold: > > 1. Structured text alternatives. > 2. Long text alternatives. Structured *and* (potentially) long. ... >> Also, regarding rendering: if the UA can't expect a HTML - in the broad >> sense, how can it usefully present description in a new browsing >> context inside the same window? On an edge, we do not want that >> @longdesc becomes some kind of image presenter tool. > > Not sure what you mean by the above. The two last screenshots in Laura's rendering page: http://www.d.umn.edu/~lcarlson/research/ld-rendering.html To present PDF, text/plain, whatever in a new browsing context in the same window, the UA should have reason to expect the content will be HTML or XMl with <html> as root element. E.g. a text plain document might have so long lines that it doesn't fit into the browsing context. Or, the encoding of the text/plain document might be dubious etc. -- Leif H Silli
Received on Wednesday, 4 May 2011 13:36:51 UTC