W3C home > Mailing lists > Public > public-html-a11y@w3.org > March 2010

Re: Please vote on the canvas accessibility proposal

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 1 Mar 2010 10:00:45 +0100
To: Charles McCathieNevile <chaals@opera.com>
Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Ian Hickson <ian@hixie.ch>, public-canvas-api@w3.org, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Message-ID: <20100301100045586381.f3e09958@xn--mlform-iua.no>
Charles McCathieNevile, Mon, 01 Mar 2010 01:52:36 +0100:
> The proposal to reinstate the HTML 4.01 version of image maps 
> requires some tweaking to some browsers. 

Btw, your message made me realize that there are probably more 
differences between HTML401 image maps and current HTML5 image maps 
than simply the part that I was occupied with, namely the thing that <a 
coords> is not allowed in HTML5. So, therefore I don't feel certain 
that is <a coords> you talk about.

But anyway, I just wanted to point out, for correctness, that in HTML5 
it is permitted to wrap an <area> element inside a <a> element, which 
should have meant that this should be quite accessible - no?

<object data="navbar1.gif" type="image/gif" usemap="#map1">
<map name="map1">
		<a title="Test link" href="guide.html">
			<area shape="rect" coords="0,0,118,28">
           		Link text</a></p></map></object>     

If HTML5 would have allowed us to duplicate @shape and @coords inside 
<a>, then we would have had a cross browser solution that worked in IE, 
Firefox and Opera. But not Webkit ... 

Here is a test case in Live DOM viewer:


Btw for IE, there is of course several issues to be aware of ... I 
won't go into that here and now. Anyway, don't know how useful this was 
for the specific canvas accessibility case.
leif halvard silli
Received on Monday, 1 March 2010 09:01:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:58:53 UTC