Re: [WSG] Images as accessible form buttons
Andreas Boehmer [Addictive Media] wrote: I then thought I should use input type=image, but realised that this doesn't work in all browsers. IE, for example, has got the nasty habbit of submitting name.x=0name.y=0 when these kind of buttons are clicked, which can make it really difficult if you have got multiple buttons in one form and you wish to detect which of them was clicked. Maybe I'm missing something, but: why not test for the presence of name.x or name.y at the receiving end then, rather than name? And, if you have multiple buttons, shouldn't it be easy enough to give them different names and test for name1.x or name2.x ? -- Patrick H. Lauke __ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com __ Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Images as accessible form buttons
On Sep 5, 2005, at 11:54 PM, Andreas Boehmer [Addictive Media] wrote: I then thought I should use input type=image, but realised that this doesn't work in all browsers. IE, for example, has got the nasty habbit of submitting name.x=0name.y=0 when these kind of buttons are clicked, which can make it really difficult if you have got multiple buttons in one form and you wish to detect which of them was clicked. The .x and .y values are according to spec; any browser that doesn't do this is broken. I suspect this is your best bet. Is the reason it's difficult to use multiple submits because you are not receiving a name=value in addition to the name.x=xxname.y=yy values? If so, then that browser is broken as well. ...an input type=image creates a submit button... http://www.w3.org/TR/html401/interact/forms.html ...a submit button is successful if clicked... http://www.w3.org/TR/html401/interact/forms.html#submit-button ...successful form elements have their values submitted paired to their names... http://www.w3.org/TR/html401/interact/forms.html#successful- controls -- Ben Curtis : webwright bivia : a personal web studio http://www.bivia.com v: (818) 507-6613 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Images as accessible form buttons
-Original Message- From: Ben Curtis [mailto:[EMAIL PROTECTED] Sent: Wednesday, 7 September 2005 2:32 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Images as accessible form buttons On Sep 5, 2005, at 11:54 PM, Andreas Boehmer [Addictive Media] wrote: I then thought I should use input type=image, but realised that this doesn't work in all browsers. IE, for example, has got the nasty habbit of submitting name.x=0name.y=0 when these kind of buttons are clicked, which can make it really difficult if you have got multiple buttons in one form and you wish to detect which of them was clicked. The .x and .y values are according to spec; any browser that doesn't do this is broken. I suspect this is your best bet. Is the reason it's difficult to use multiple submits because you are not receiving a name=value in addition to the name.x=xxname.y=yy values? If so, then that browser is broken as well. When you say it's broken you mean it doesn't adhere to the standards? Well, that seems to be the case with IE 5 and IE 6. These browsers only submits name.x=xxname.y=yy values, no name=value in the querystring. Firefox on the other hand submits both. Whether you call it broken or not, the fact seems to remain that IE doesn't handle these buttons correctly, which in the long run means they are inaccessible. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
