E-mail List Archives
Thread: Form objects and Section 508
Number of posts in this thread: 2 (In chronological order)
From: Kevin Spruill
Date: Mon, Mar 25 2002 3:14PM
Subject: Form objects and Section 508
No previous message | Next message →
Hello all,
Sorry for the mime mail earlier...
In the midst of a methodology debate, and am interested in practical
feedback. The Section 508 guidelines state:
"(n) When electronic forms are designed to be completed on-line, the
form shall allow people using assistive technology to access the
information, field elements, and functionality required for completion
and submission of the form, including all directions and cues." - and
the training materials then go on to discuss proper use of labels, etc.
to assure accessibility. The training materials also say:
"Don't configure the fields with default text entry, since an AT user
expects to encounter blank space for a field so he can enter his own
information"
Which is fine except for the fact that it contradicts the W3C
recommendation which states:
"10.4 Until user agents handle empty controls correctly, include
default, place-holding characters in edit boxes and text areas."
Now, without getting into a spirit vs. letter of the law argument, I'm
wondering just which approach is best for the user? Any thoughts?
Thanx in advance!
Kevin Spruill
National Library of Medicine
OCCS
= EMAIL ADDRESS REMOVED =
(301) 402-9708
(301) 402-0367 (fax)
www.nlm.nih.gov
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
From: Mark Rew
Date: Tue, Mar 26 2002 4:49AM
Subject: Re: Form objects and Section 508
← Previous message | No next message
When I'm using a screen reader, Jawss 4.0, to fill out a Web based form what
is important is hearing all of the necessary information to understanding the
edit area. Nothing is more frustrating than to tab to a location and only
hear, "edit." If the input has default text, it needs to be easy to modify if
required.
What is very confusing is when I tab to a combination box and only hear such
information as the numbers 1, 2, ... Or, only the words YES, NO. I need to
know what the question is that I'm being asked to answer. This is wwhere
labels are really helpful.
So, to answer the question below, the text in the edit field of a form is only
helpful if it gives information that assist with understanding what the edit
area is for.
Mark Rew
----- Original Message -----
From: "Kevin Spruill" < = EMAIL ADDRESS REMOVED = >
To: < = EMAIL ADDRESS REMOVED = >
Sent: Monday, March 25, 2002 5:14 PM
Subject: Form objects and Section 508
> Hello all,
>
> Sorry for the mime mail earlier...
>
> In the midst of a methodology debate, and am interested in practical
> feedback. The Section 508 guidelines state:
>
> "(n) When electronic forms are designed to be completed on-line, the
> form shall allow people using assistive technology to access the
> information, field elements, and functionality required for completion
> and submission of the form, including all directions and cues." - and
> the training materials then go on to discuss proper use of labels, etc.
> to assure accessibility. The training materials also say:
>
> "Don't configure the fields with default text entry, since an AT user
> expects to encounter blank space for a field so he can enter his own
> information"
>
> Which is fine except for the fact that it contradicts the W3C
> recommendation which states:
>
> "10.4 Until user agents handle empty controls correctly, include
> default, place-holding characters in edit boxes and text areas."
>
> Now, without getting into a spirit vs. letter of the law argument, I'm
> wondering just which approach is best for the user? Any thoughts?
>
> Thanx in advance!
>
>
> Kevin Spruill
> National Library of Medicine
> OCCS
> = EMAIL ADDRESS REMOVED =
> (301) 402-9708
> (301) 402-0367 (fax)
> www.nlm.nih.gov
>
>
> ----
> 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/