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_that_allows_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

Received on Wednesday, 14 March 2007 03:55:24 UTC