- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Fri, 7 Sep 2012 17:48:55 -0500
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Adrian Roselli <Roselli@algonquinstudios.com>, Mathew Marquis <mat@matmarquis.com>, Peter Winnberg <peter.winnberg@gmail.com>, Steve Faulkner <faulkner.steve@gmail.com>, HTML WG <public-html@w3.org>, "public-respimg@w3.org" <public-respimg@w3.org>
Hi Leif, You wrote: > I think: Mat changed his direction not only > because of temporary "lack of support" complexity *but also* because > he saw that their model (double @alt) would *end up* complex, once > <picture> was supported. Yes, double alt would be complex. > It is a move towards allowing alternative text via fallback markup > content (as opposed to just via attributes), and hence a postive step. An element like <desc> would provide a semantic holder for rich text on-page long descriptions. However, it would be hamstrung to on-page descriptions. It would not be a direct off-page long description that could be applied globally across multiple sites, or across an entire site, or across a subset of pages. http://www.d.umn.edu/~lcarlson/research/constriants/separate-doc.html > <picture> > <img src=file alt=text longdesc=description.url > > </picture> > > QUESTION: How would users of the equipment listed on your > research page access that longdesc? > ANSWER: It would be broken in some of them... > > Browsers: I believe it would not work in a single one of the browsers > that you list. E.g. it would not work in iCab. Why not? > Because you cannot access the context menu for an image > that is hidden behind another element. This is incorrect Leif. It seems to work in all of them that I tested. Here is a test page: http://www.d.umn.edu/~lcarlson/research/constriants/picture-test.html HTML: <picture> <img src="images/external.png" alt="One external file provides and controls the description for multiple docs" longdesc="ld/separate-doc.html"> </picture> I haven't found any instances where the above HTML code differs in functionality from the what is listed on the research page. Some results with screen shots: WORKS in iCab natively (screenshot: http://www.w3.org/html/wg/wiki/images/4/41/Icab.png ) WORKS in Opera natively (screenshot: http://www.w3.org/html/wg/wiki/images/f/f2/Opera.png ) WORKS in Opera w/tellmemore (screenshot: http://www.w3.org/html/wg/wiki/images/2/26/Tellmemore.png ) WORKS in Firefox w/Patrick's longdesc (screenshot http://www.w3.org/html/wg/wiki/images/b/bf/Firefox.png ) WORKS in Firefox w/Anthony's longdesk (screenshot: http://www.w3.org/html/wg/wiki/images/c/c1/Longdesk.png ) WORKS in Safari w/longdesc favelet (screenshot: http://www.w3.org/html/wg/wiki/images/a/af/Safari.png ) WORKS in Chrome w/longdesc favelet (screenshot: http://www.w3.org/html/wg/wiki/images/8/89/Chrome.png ) Gez Lemon tested the page with JAWS and IE, and the longdesc attribute is revealed and works correctly with JAWS (opened this page when he activated it: http://www.d.umn.edu/~lcarlson/research/constriants/ld/separate-doc.html). He also tested it with Jim Thatcher's longdesc favelet and that found and revealed it too. Best Regards, Laura -- Laura L. Carlson
Received on Friday, 7 September 2012 22:49:23 UTC