Hi,
Doesn't look like valid code to me.
Stuart
On Thu, April 12, 2007 2:07 pm, Nick Fitzsimons wrote:
On 12 Apr 2007, at 13:34:06, Patrick Lauke wrote:
I'm not making assumptions. I'm saying that, for sighted users,
having a text input box with no visible label and a button that
says
On 14 Apr 2007, at 07:25:29, Stuart Foulstone wrote:
Hi,
Doesn't look like valid code to me.
Stuart
!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN http://www.w3.org/
TR/html4/strict.dtdhtml
head
titleblah/title
/head
body
form action=
div
label for=searchBox
input type=text
Mmm,
not really the kind of label tags we were discussing.
Stuart
On Sat, April 14, 2007 9:08 am, Matthew Pennell wrote:
PS: Link for you: http://alistapart.com/articles/alphabet
;)
***
List Guidelines:
Bojana Lalic wrote:
Hi all
Accverify fails my code because my input element does not contain the
alt attribute or label.
I don't want any text displayed before or after the query text input
element. Should I wrap a label around the input element and then hide it
using css? How do I get
Nick Fitzsimons
Surely
label for=searchBox
input type=text id=searchBox name=q
button type=submitSearch/button
/label
would therefore keep everybody happy?
Depends on AT support (whether or not a screenreader would actually be able to
make sense of this construct and expose
Hi,
The labels are there for accessibility reasons, if you don't want to
design for accessibility, don't pretend to.
Stuart
On Thu, April 12, 2007 1:55 am, Bojana Lalic wrote:
Hi all
Accverify fails my code because my input element does not contain the
alt attribute or label.
I don't
The labels are also clickable to focus on their respective fields so I
wouldn't say they are purely accessibility oriented in nature.
Stuart Foulstone wrote:
Hi,
The labels are there for accessibility reasons, if you don't want to
design for accessibility, don't pretend to.
Stuart
On Thu,
Hi,
Since the ability to click on the label (or field) to put focus on the
field is an accessibility feature of forms, I don't really understand your
point.
Stuart
On Thu, April 12, 2007 9:40 am, Jixor - Stephen I wrote:
The labels are also clickable to focus on their respective fields so I
I would refer to that as usability.
Stuart Foulstone wrote:
Hi,
Since the ability to click on the label (or field) to put focus on the
field is an accessibility feature of forms, I don't really understand your
point.
Stuart
On Thu, April 12, 2007 9:40 am, Jixor - Stephen I wrote:
The
Stuart Foulstone
If you're only concerned about providing form accessibility for
screenreaders, and no other disability, you could use the
method below or
a transparent.gif with appropriate alt-text would work too.
Not necessarily just for screenreader accessibility. If the input itself is
Sorry, I thought we were discussing labels for form input boxes (not just
one-box input search forms).
However, generally speaking, making assumptions about accessibility based
on the visual positioning of elements in a logical common place used by
most other sites is not a good idea.
Better to
On 12 Apr 2007, at 13:34:06, Patrick Lauke wrote:
I'm not making assumptions. I'm saying that, for sighted users,
having a text input box with no visible label and a button that
says Search immediately next to it is labelling enough.
Surely
label for=searchBox
input type=text
Nick Fitzsimons
Surely
label for=searchBox
input type=text id=searchBox name=q
button type=submitSearch/button
/label
would therefore keep everybody happy?
Depends on AT support (whether or not a screenreader would actually be able to
make sense of this construct and expose
Bojana Lalic wrote:
I don’t want any text displayed before or after the query text input
element. Should I wrap a label around the input element and then hide it
using css? How do I get around this accessibility issue?
Me personally, I setup my form normally using label/input, then apply
14 matches
Mail list logo
