Re: [WSG] Duplicate buttons
Unfortunately browser like lynx ignore tabindices, and some older versions of Mozilla get it wrong and make it impossible to tab to anything which doesn't have a tabindex as soon as you use elements with tabindex. Moreover, especially on long forms, even if you could rely on tabindex, you'd start pulling your hairs out having to add tabindices to every single form element (as otherwise the browser will still cycle through the ones with a tabindex, no matter how high/low you set it, before tabbing through the non-tabindexed elements). So overall, I still don't think that's a viable solution. Why not go for skip to the end of the form type links (they can even be graphical for sighted users)? Seems to me these would be the least bothersome, and not about to break even in older browsers... Patrick Mordechai Peller wrote: Patrick H. Lauke wrote: well, imagine the user has a screenreader or braille display and is tabbing through the form . they end up on the first submit button, and have no way of knowing that there's more after that button, so they submit it at the first intermediate step...not good. That's not a problem. All you need to do is make sure the tab indexes are higher than than the last element. Also, iirc, setting the tab index to -1 will make it unaccessible by tabbing; just make sure you don't do that to the last one. ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** -- _ 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 ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Duplicate buttons
I have found that having multiple submit buttons can cause problems for screen reader users. A possible solution is to place the both submit buttons at the bottom of the form (within the code) and use CSS to position one of the buttons in the middle/or wherever (visually) of the form. As screenreaders read the page as it is written in the code (ignoring css positioning) a screen reader user will not encounter the submit button(s) until the end of the form. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Taco Fleur [EMAIL PROTECTED]To: [EMAIL PROTECTED] net.au cc: Sent by: Subject: [WSG] Duplicate buttons [EMAIL PROTECTED] group.org 27/08/2004 08:31 PM Please respond to wsg I have been putting duplicate buttons on one form when its a long form, so the user does not have to scroll. I have been told its not good for accessibility, what's the go? Taco Fleur Tell me and I will forget Show me and I will remember Teach me and I will learn ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Duplicate buttons
Patrick H. Lauke wrote: well, imagine the user has a screenreader or braille display and is tabbing through the form . they end up on the first submit button, and have no way of knowing that there's more after that button, so they submit it at the first intermediate step...not good. That's not a problem. All you need to do is make sure the tab indexes are higher than than the last element. Also, iirc, setting the tab index to -1 will make it unaccessible by tabbing; just make sure you don't do that to the last one. ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Duplicate buttons
Taco Fleur wrote: I have been putting duplicate buttons on one form when its a long form, so the user does not have to scroll. I have been told its not good for accessibility, what's the go? While the duplication does reduce accessibility/usability in some ways, but it also adds in others. IMO, there is a net gain. ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Duplicate buttons
well, imagine the user has a screenreader or braille display and is tabbing through the form . they end up on the first submit button, and have no way of knowing that there's more after that button, so they submit it at the first intermediate step...not good. why not split up the form over multiple screens instead (or even better, offer two options: multi-page or one single long form - with only one submit button at the end). additionally, you could provide an access key for the submit button, enabling keyboard users to quickly skip to the end and submit. and another thought: skip links to go to the end of the form (which benefit all users, and do pretty much what you're aiming to do). but i'd definitely recommend not having intermediate buttons... Patrick H. Lauke Taco Fleur wrote: I have been putting duplicate buttons on one form when its a long form, so the user does not have to scroll. I have been told its not good for accessibility, what's the go? *Taco Fleur* Tell me and I will forget Show me and I will remember Teach me and I will learn -- _ 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 ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
