RE: advisory tech for 2.5.1

Hi,

I would prefer not to use John's example, for the following reasons:

1. The technique described seems to be a client-side Javascript that
runs on the current page. If errors are hard coded, hidden with CSS and
shown as needed, then all of those error messages would be shown when
the author's style sheet is not used (as may be done by users requiring
alternate visual presentation) as soon as the page is loaded.

2. Visual users would find this technique annoying since they would not
necessarily need to return to the list of errors. If good usability was
being used then they would not need this list at all (because they would
have each incorrect field highlighted in context).

Also - do we need to mention that these techniques do not work without
Javascript and that a backup should be in place?

Sofia


-----Original Message-----
From: public-wcag-teamc-request@w3.org
[mailto:public-wcag-teamc-request@w3.org] On Behalf Of David MacDonald
Sent: Thursday, 15 March 2007 3:13 AM
To: 'Slatin, John M'; Sofia Celic; public-wcag-teamc@w3.org
Subject: RE: advisory tech for 2.5.1


Do you mind if I post that in the technique John?

access empowers people...
        ...barriers disable them...

www.eramp.com

-----Original Message-----
From: public-wcag-teamc-request@w3.org
[mailto:public-wcag-teamc-request@w3.org] On Behalf Of Slatin, John M
Sent: Wednesday, March 14, 2007 11:24 AM
To: David MacDonald; Sofia Celic; public-wcag-teamc@w3.org
Subject: RE: advisory tech for 2.5.1


For what it's worth, I recently evaluated a site that handled errors as
follows:

1. A script automatically set focus to a text link that said "Errors
have occurred."
2. The link went to the first item in an ordered list of descriptive
error messages." Each description was a link to the control where the
error had occurred.
3. After correcting the error, focus was returned to the original
message (Errors have occurred). This link went to a list of links to the
remaining errors.
Repeat as needed.

I found it clear and helpful.

I believe what they did was to hard-code all the error messages in the
source and set them to display: none, then show them when errors
occurred.

John

"Good design is accessible design."

Dr. John M. Slatin, Director
Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, fax 512-495-4524
email john_slatin@austin.utexas.edu
Web http://www.utexas.edu/research/accessibility



-----Original Message-----
From: public-wcag-teamc-request@w3.org
[mailto:public-wcag-teamc-request@w3.org] On Behalf Of David MacDonald
Sent: Wednesday, March 14, 2007 8:50 AM
To: 'Sofia Celic'; public-wcag-teamc@w3.org
Subject: RE: advisory tech for 2.5.1



Hi Sophia

I was thinking of a popup client side script with the error message. I
recently came across that on a site I was evaluating for a bank. It was
more accessible than the pages that put the errors at the top of the
page because the popup brought focus to the error message which was in
the popup. My blind screen reader evaluator really liked it.

I've changed the example to remove the part about the error being after
the submit button. Does it work now?

David

access empowers people...
        ...barriers disable them...

www.eramp.com
-----Original Message-----
From: public-wcag-teamc-request@w3.org
[mailto:public-wcag-teamc-request@w3.org] On Behalf Of Sofia Celic
Sent: Tuesday, March 13, 2007 11:55 PM
To: David MacDonald; public-wcag-teamc@w3.org
Subject: RE: advisory tech for 2.5.1


Hi David and all,

I know this has already been discussed and surveyed, but here is a
comment if you are able to consider the following at this stage:

I am unsure about including Example 2 as is. In my experience, I would
say that screen reader users will most likely miss the text message that
is inserted into the document after the submit button. Client side
scripting will not alert the user to the change (generally speaking) and
the user is likely waiting for a new page load the reader to begin
reading the page. A more effective technique would be use an alert box
because the user can not miss it.

The above would require changes to the procedure section too.

I also made some small edits to the Description part of the page (fixing
spelling errors and the like).

Sofia

________________________________

From: public-wcag-teamc-request@w3.org on behalf of David MacDonald
Sent: Tue 13/03/2007 3:47 AM
To: public-wcag-teamc@w3.org
Subject: advisory tech for 2.5.1



I Had and action to turn the 2.5.1 suffient proposal into an advisory
for 2.5.1 It is here:



http://trace.wisc.edu/wcag_wiki/index.php?title=Creating_a_mechanism_tha
t_al
lows_users_to_jump_to_errors



or



http://tinyurl.com/ytk95o





David MacDonald

access empowers people...

        ...barriers disable them...



www.eramp.com <http://www.eramp.com/>


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.9/719 - Release Date:
3/12/2007 8:41 AM




--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.11/721 - Release Date:
3/13/2007 4:51 PM


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.11/721 - Release Date:
3/13/2007 4:51 PM




--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.11/721 - Release Date:
3/13/2007
4:51 PM


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.11/721 - Release Date:
3/13/2007
4:51 PM






________________________________

<< ella for Spam Control >> has removed 505 Spam messages and set aside
255 Later for me
You can use it too - and it's FREE!  www.ellaforspam.com

Received on Thursday, 15 March 2007 03:33:20 UTC