W3C home > Mailing lists > Public > public-html@w3.org > June 2008

Re: Text presentation of image maps with <object> (detailed review of Semantics)

From: Simon Pieters <simonp@opera.com>
Date: Thu, 05 Jun 2008 13:24:55 +0200
To: "Ian Hickson" <ian@hixie.ch>
Cc: public-html <public-html@w3.org>
Message-ID: <op.ub9wntktidj3kv@zcorpandell.linkoping.osa>

On Thu, 05 Jun 2008 11:33:09 +0200, Ian Hickson <ian@hixie.ch> wrote:

> On Wed, 8 Aug 2007, Simon Pieters wrote:
>> (This is part of my detailed review of the Semantics and structure of
>> HTML elements section.)
>> The spec says about image maps:
>>    If the user agent intends to show the text that the img or input
>>    element represents, then it must use the following steps.
>>    Note: In user agents that do not support images, or that have images
>>    disabled, object elements cannot represent images, and thus this
>>    section never applies (the fallback content is shown instead). The
>>    following steps therefore only apply to img and input elements.
>> I think it should apply when an <object> doesn't represent an image
>> (perhaps regardless of what else it represents instead). Otherwise using
>> image maps together with <object> is inherently inaccessible when images
>> are disabled (unless the author jumps through hoops to duplicate the
>> links as both <area> and <a> inside the object, which I don't think is
>> realistic or particularly elegant).
> The problem is that I don't understand how it would work. I can  
> understand
> an image's alt text being displayed as a link and making that link bring
> up a window with a further list of links,

Why would you bring up a window rather than just show the list of links  
directly on the page?

> but what do you do when the
> object includes a form, a plugin, a video, and a dozen other links?

Show them in addition to the links defined by <area> elements?

> Inserting text into the page is a non-starter (it would break the  
> intended
> rendering in author-uncontrolled ways).

Generally, authors only care about the intended rendering when images are  

> What else could you do?

Hmm. Make usemap not work with <object> at all? :-) Or would dropping  
support for it break too much Web content?

Simon Pieters
Opera Software
Received on Thursday, 5 June 2008 11:25:42 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:34 UTC