- From: Robert Burns <rob@robburns.com>
- Date: Tue, 14 Aug 2007 22:19:56 -0500
- To: Jason White <jason@jasonjgw.net>
- Cc: public-html <public-html@w3.org>
On Aug 14, 2007, at 10:02 PM, Jason White wrote: > > There is a significant accessibility problem associated with the > proposal to > drop USEMAP on INPUT, namely that if an author desires to use an > image map as > a form input field, the only alternative would then be to apply > @ismap (a > server-side image map). > > Server-side image maps present an accessibility obstacle to those > who are > unable to operate a pointing device. This is why client-side image > maps are > preferred and ought to be encouraged, and why @alt is defined for > <area>. > > The proposal to omit @usemap on <input> would eliminate the accessible > solution, whilst leaving the inaccessible option of a server-side > image map > intact. > > I propose that either @usemap should not be dropped, or both it and > @ismap > should be omitted. I agree with Jason 1005. I'd like to add that @usemap on INPUT is really the same thing as @usemap on IMG. Its the same feature supported in a polymorphic manner. Itt may not have been implemented correctly in UAs, however that can be dealt with by filing bug reports. The fact that it's not correctly implemented in UAs may also pint to the reason and the solution to why it has not been widely used by authors. If we're going to support @usemap on IMG (and I think we should) then we should also support @usemap on INPUT. I often surprised at the lack of imagination here, but an obvious use-case for this would be to submit form data based on where a user clicks on the INPUT image. This could be used in games, it could be used to provide GUI selection of items, it could be used in all sorts of ways (if it were implemented correctly). Take care, Rob
Received on Wednesday, 15 August 2007 03:20:09 UTC