W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2003

RE: using a form field for terms & conditions

From: Jon Hanna <jon@spin.ie>
Date: Fri, 15 Aug 2003 14:31:39 +0100
To: "WAI Mailing list \(E-mail\)" <w3c-wai-ig@w3.org>
Message-ID: <NDBBLCBLIMDOPKMOPHLHKEJEFHAA.jon@spin.ie>

> Sticking the T&Cs in a <div> with an "overflow:auto" CSS rule and
> set dimensions can
> achieve the same effect whilst avoiding the problems outlined
> previously (although on older
> browsers the styling might not work and the div will just grow
> vertically with the ammount
> of text etc contained within...but at least it's still perfectly
> usable/accessible despite
> the fact that it won't look that "pretty" anymore).

I agree wholeheartedly, this is the best way to do it.

> And once you stop using textarea, there is no reason anymore to
> actually use
> a form

Forms are the only way to use normal HTML to send a POST (there are a few
more convoluted ways, such as javascript submitting a hidden form or
javascript transmitting an XML document). Therefore without POST you are
left with GET and the semantics of GET don't agree to anything; GET is
"looking" where POST is "doing".
See <http://www.w3.org/TR/webarch/#safe-interaction> and
<http://www.w3.org/2001/tag/doc/whenToUseGet.html>.

Two cases where the semantics have a practical effect is with robots and
links that bypass the T&C page. In these cases the T&C cannot be agreed to,
as they haven't been seen.

Users can be held accountable for what they POST but not for what they GET.
Received on Friday, 15 August 2003 09:27:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:10 GMT