Return-Path: 
 <dev-return-54161-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 21176 invoked from network); 15 Jan 2004 22:23:18 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 15 Jan 2004 22:23:18 -0000
Received: (qmail 24610 invoked by uid 500); 15 Jan 2004 22:23:02 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 24560 invoked by uid 500); 15 Jan 2004 22:23:02 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 24547 invoked from network); 15 Jan 2004 22:23:02 -0000
Received: from unknown (HELO mhub-c5.tc.umn.edu) (160.94.128.35)
  by daedalus.apache.org with SMTP; 15 Jan 2004 22:23:02 -0000
Received: from [66.41.41.255] by mhub-c5.tc.umn.edu with ESMTP for
 dev@cocoon.apache.org; Thu, 15 Jan 2004 16:16:34 -0600
Message-Id: <40071113.30202@umn.edu>
Date: Thu, 15 Jan 2004 16:15:47 -0600
From: Tony Collen <colle006@umn.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Woody and WAI
References: <CED69583-4797-11D8-954B-0003935AD2EE@media.demon.co.uk>
In-Reply-To: <CED69583-4797-11D8-954B-0003935AD2EE@media.demon.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Jeremy Quinn wrote:

> Hi All,
>
> I am in the process of getting some Woody forms approved as WAI 
> compliant.
>
>     http://www.w3.org/WAI/
>
> While WAI may not be everybody's cup of tea ..... in certain sectors 
> it is a common requirement .... and it is certainly not a bad selling 
> point.
>
>
> There are three issues which come up regularly with basic Woody forms:
>
> 1) Provide an explicit label for each form control. (Level 2)
> 2) Include default, place-holding characters in edit boxes and text 
> areas. (Level 3)
> 3) Provide a summary for tables. (Level 3)
>
>

<snip>

> Issue (2), placeholder text, is slightly more complicated. I think we 
> would have to introduce the concept of a default value to Woody's 
> field markup, with the *option* to automatically invalidate fields 
> which had their default values in.
>
This would be nice, I know there's a lot of work left to go on the 
client-side aspect of Woody/CForms.

As far as setting default values in a form, you can do something like 
this in your flow:

bean = new Packages.foo.myBean();
bean.setBlah("default value");
form.load(bean);
form.showForm("whatever");

It would be nice to be able to set a default value for a field however.

> Furthermore, I suspect it would be best if such fields had JavaScript 
> like the following in them, when they have been populated with a 
> default value that is not allowed by the validation:
>
> <input name="sample-field"
>     value="default value"
>     onfocus="if (this.value == 'default value') this.value = '';"
>     onblur="if (this.value == '') this.value = 'default value';"
>     etc.
> />
>
> Issue (3) making sure tables have summaries is easy:
>
>     <table summary="this is a summary of the table's contents">
>
> Several widgets in Woody make Tables, I propose that their 'hint' 
> could be used as the summary.


+1 for the hint going into the table summary.

Tony