That's really interesting Mike. After visiting a conference a couple of years ago where a demonstration was given on screen reader use of forms, I have been wrapping the input in a label and having a for attribute set. Both were presented as being equally accessible (the demo must have been in JAWS), and wrapping the input made it easier to style.
I'd be very interested in reading your article when it's ready :o) Rachel May P +64-4-384-3546 E [EMAIL PROTECTED] The Survey Company Level 1, 50 Manners St PO Box 6859, Marion Square Wellington www.thesurveycompany.com The Survey Company is a division of Heliocell Ltd. PLEASE NOTE: This email message and accompanying data may contain information that is confidential and subject to legal privilege. If you are not the intended recipient you are notified that any use dissemination distribution or copying of this message or data is prohibited. If you have received this email message in error please notify us immediately and erase all copies of the message and attachments. Any views expressed in this message are those of the individual sender, except where the sender states them, with requisite authority, to be those of Heliocell Ltd. The recipient stated is the sole intended recipient and this email is not to be forwarded or shared digitally without the permission of the sender. Thank you -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike at Green-Beast.com Sent: Friday, 8 February 2008 11:24 a.m. To: [email protected] Subject: Re: [WSG] Styling forms Hello Thomas, > How does screenreaders treat using just > <label><input/></label>? I'm writing an article on just that thing now. Jaws is okay with it, but Windows Eyes chokes on it. That in itself may not be too-too important due to the number of users, but I'm 99.99% sure that Safari on Mac users will have difficulty (at best) actually inputting content in such a form input. I can't replicate this on Safari for Windows, but I have gotten lots of feedback to go on. I actually just updated both of my version two contact forms today to correct this (v3 was already fixed). I've been fixing forms all day actually. I have come to the conclusion that the only proper method is... <label for="foo">Foo Text</label> <input id="foo"> Though I suppose <input alt="Foo Text"> would also be okay. Cheers. Mike ----- Original Message ----- From: "Thomas Thomassen" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, February 07, 2008 4:36 PM Subject: Re: [WSG] Styling forms hm... this thread has given me a thinker. How does screenreaders treat using just <label><input/></label>? <form> <fieldset> <label>Foo: <input id="foo"/></label> <label>Bar: <input id="bar"/></label> </fieldset> </form> How will it present the form? If it's all inline, will it be read continuous, or will there be a break between the elements? ----- Original Message ----- From: Joe Ortenzi To: [email protected] Sent: Thursday, February 07, 2008 9:31 PM Subject: Re: [WSG] Styling forms Well done Alexey! Are we not confusing semantics with presentational here? if it is OK to strip the presentational out of a list element (when we use a list for a navigation group and want our navigation elements in a row instead of a column) what is wrong with supplanting the inline quality of a label/input group by designating it a block element, and then group several form elements, or even each label input group with fieldsets? BTW: <br /> is the equivalent of a force carriage return and thus belongs within paragraphs, i thought! Joe On Feb 7 2008, at 19:55, Алексей Новиков wrote: On Behalf Of Thierry Koblentz Sent: Thursday, February 07, 2008 10:29 AM To: [email protected] Subject: Re: [WSG] Styling forms TK> fwiw, I think BRs are the perfect fit. BRs? Are BRs semantically correct? I believe they aren't. -- Regards, Alexey Novikov http://studiomade.ru ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* Joe Ortenzi [EMAIL PROTECTED] www.joiz.com ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
