Good day,
When making a form in Dreamweaver it puts in id=same as name in to
every form item. When I take out all the id attributes the form still
works. Why are the id attributes being put in by DW and, more
importantly, is there an accessibility issue if I take them out?
i.e. -
Those IDs can be used as hooks to allow CSS and JavaScript to interact
with your individual form elements.
---
Dale Cruse
617.640.0856
http://www.DaleJCruse.com
On Wed, Aug 19, 2009 at 11:37 AM, Erickson, Kevin (DOE)
kevin.erick...@doe.virginia.gov wrote:
Good day,
When making a form in
On 19 Aug 2009, at 16:37, Erickson, Kevin (DOE) wrote:
When making a form in Dreamweaver it puts in id=same as name in to
every form item. When I take out all the id attributes the form
still works. Why are the id attributes being put in by DW and, more
importantly, is there an
I think the ID's are required for the 'for' attribute to work for labels,
which enables the their clickability. When these labels are clicked on they
focus on the element whose ID is in the for attribute.
label for=CommentsEnter you comments:/label
Plus having ID's associated allows for more
Correct the ID's are required for the for attribute of the LABEL tag to
work; but each ID must be unique.
Best Regards,
Nate Hanna
On Wed, Aug 19, 2009 at 11:54 AM, James O'Neill freexe...@gmail.com wrote:
I think the ID's are required for the 'for' attribute to work for labels,
which
On a slightly related topic, I have wrapped inputs inside of labels
for browser compatibility for the label clickability/focus issue
(based on some research some time ago), but have just read for the
first time recently, that this is not a good idea. Any thoughts?
On Wed, Aug 19, 2009 at 11:54
Hmmm... I do not really remember.
I have used both together and separately at different times.
By enclosing a form control with a label you will have a little more control
over relative styling since you could something like this:
label:hover input {outline:solidl}
or have more precise
Yeah. That's the issue that was brought up in the recent article I
read. Apparently it's possible for some screen readers to get
confused. I have not tested it. Was wondering if anyone else knew
anymore info on this...
On Wed, Aug 19, 2009 at 2:54 PM, Erickson, Kevin
On 19 Aug 2009, at 19:35, Tom Livingston wrote:
On a slightly related topic, I have wrapped inputs inside of labels
for browser compatibility for the label clickability/focus issue
(based on some research some time ago), but have just read for the
first time recently, that this is not a good
Have you tested it out with any screen readers? I would like to hear
about the results.
Kevin
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Tom Livingston
Sent: Wednesday, August 19, 2009 2:36 PM
To: wsg@webstandardsgroup.org
The reason I use this was because I found an easy way to style forms
that included the broader compatibility for the clickability of labels
for focus with the flexibility of layout with the inclusion of a span
like:
label for=name
spanFirst Name/span
input type=text /
/label
I use this a lot for
For clarity, I submit this edit:
label for=name
spanFirst Name/span
input type=text id=name /
/label
The for attribute matches the input ID. Always.
On Wed, Aug 19, 2009 at 3:09 PM, Tom Livingstontom...@gmail.com wrote:
The reason I use this was because I found an easy way to style forms
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Tom Livingston
Sent: 19 August 2009 20:10
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessible Forms
The reason I use this was because I found an easy way to style forms that
On 19/08/2009 20:04, David Dorward wrote:
On 19 Aug 2009, at 19:35, Tom Livingston wrote:
On a slightly related topic, I have wrapped inputs inside of labels
for browser compatibility for the label clickability/focus issue
(based on some research some time ago), but have just read for the
Wow! So what is the best practice???
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Steve Green
Sent: Wednesday, August 19, 2009 3:59 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] Accessible Forms
-Original Message-
All,
The following article shed light on both mark-up and styling.
http://www.sitepoint.com/article/fancy-form-design-css/
It should help.
C,
On Aug 19, 2009, at 1:11 PM, Erickson, Kevin (DOE) wrote:
Wow! So what is the best practice???
-Original Message-
From:
Good question!
Well, if IE6 was the reason for nesting to get clickability to work,
then to heck with that. I just wanna know the best way, without the
span to control the label text, to get label text NEXT TO the input,
with nice even spacing and flexible control.
On Wed, Aug 19, 2009 at 4:11
I have two simple forms. Which is better?:
http://www.doedev.vi.virginia.gov/z_testing_area/kevin/form_mail_vi/form
_mailer4.shtml
Code:
form name=form_submit method=post
action=/home_files/forms/form_mail_template.cfm
p
span id=sprytextfield1
FYI- I did replace align=right align=center with CSS styling.
-Original Message-
From: Erickson, Kevin (DOE)
Sent: Wednesday, August 19, 2009 4:33 PM
To: 'wsg@webstandardsgroup.org'
Subject: RE: [WSG] Accessible Forms
I have two simple forms. Which is better?:
FYI- I did replace align=right align=center with CSS styling.
-Original Message-
From: Erickson, Kevin (DOE)
Sent: Wednesday, August 19, 2009 4:33 PM
To: 'wsg@webstandardsgroup.org'
Subject: RE: [WSG] Accessible Forms
I have two simple forms. Which is better?:
Here are some best practices examples. The encapsulation method has
some side effects that any content in text form controls becomes part
of the label, which can be confusing to speech users.
http://html.cita.illinois.edu/nav/form
Jon
On Wed, Aug 19, 2009 at 2:04 PM, David
Hi,
I recommend this publication http://www.rosenfeldmedia.com/books/webforms/
. It just arrived from Amazon
today, and is very informative.
C
On Aug 19, 2009, at 1:42 PM, Erickson, Kevin (DOE) wrote:
FYI- I did replace align=right align=center with CSS styling.
-Original
22 matches
Mail list logo
