WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: JAWS and online forms question

for

From: John Foliot - bytown internet
Date: Feb 20, 2003 5:18PM

Lisa,

define "long".

If it's not *too* long, you might consider wrapping the entire expalation in
the <label> element, especially if it is crucial information. Using Fields
sets may also aid in navigating your form:

<form action="foo">

<fieldset title="Field One">
<legend>Field One</legend>
<p>This is a long instruction on how to correctly fill out field 1, plus any
reference information which might be needed.</p>

<label for="field_one">Field1 Label:</label><input type="text"
name="field_one" id="field_one" title="Possible inclusion of explanation
text.">
</fieldset>

<fieldset title="Field Two">
<legend>Field Two</legend>
<label for="field_two"><p>This is a long instruction on how to correctly
fill out
field 2, plus any reference information which might be needed.</p>

Field2 Label:</label><input type="text" name="field_two" id="field_two">
</fieldset>

</form>


I tested this in HPR, and the second fieled carried the explanation forward
when using "Link" mode (similar to JAWs Forms Mode)

Just a thought... requires real world testing

JF

> -----Original Message-----
> From: Miller, Lisa F. (LMS) [mailto: <EMAIL REMOVED> ]
> Sent: Thursday, February 20, 2003 4:35 PM
> To: Web AIM Forum (E-mail)
> Subject: JAWS and online forms question
>
>
> We are developing an online form, and are having problems navigating thru
> the from with JAWS. There are a number of labeled input fields,
> which each
> have text instructions preceeding them, such as:
>
> ==> This is a long instruction on how to correctly fill out field 1, plus any
> reference information which might be needed.
>
> Field1 Label: ___________
>
> This is a long instruction on how to correctly fill out field 2, plus any
> reference information which might be needed.
>
> Field2 Label: ____________
>
> ==>
> When our tester navigates this page with JAWS, the instructions lines are
> skipped because it is navigating thru the input fields only - to get the
> text, he has to change modes, which a blind person would not know to do -
> there is no indication to the user that the text is there.
>
> Right now the page is built with one set of FORM tags - is there any way,
> other than wrapping each individual input field with its own FORM tag, to
> get JAWS to read the instruction text? We are debating placing the text
> into read only textareas, but this would not be our first choice. Has
> anyone else ran across this - maybe already solved this for us?
>
> Thanks,
>
> Lisa F. Miller
> BWXT Y-12 - Technical Computing
> Email: <EMAIL REMOVED>
>
>
> ----
> To subscribe, unsubscribe, or view list archives,
> visit http://www.webaim.org/discussion/
>
>
>
>



----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/