I would recommend a div element with a fixed height and overflow:auto.
Use of a textarea would not be semantically correct because it is not user
input. The only reason that leads to its use is that is gives you a scroll
bar for free, however this can be achieved with relative ease as mentioned
before. The submission problem is more of a side-effect than a root problem.
div.TermsAndConditions
{
height: 8em;
overflow: auto;
}
<div class="TermsAndConditions">
<p>Your text here.</p>
<p>And here ...</p>
</div>
If required, you could also have a checkbox where they acknowledge their
acceptance of the terms. This would be implemented as with any other form
field because it semantically is user input.
Thanks,
Tatham Oddie
call:+61414275989, call:+61280113982, skype:tathamoddie,
msn:[EMAIL PROTECTED], tatham.oddie.com.au
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Jason Pruim
Sent: Tuesday, 30 September 2008 11:46 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Incorporating Terms and Cons in signup page
On Sep 30, 2008, at 9:15 AM, John Unsworth wrote:
> Hi WSG,
> I'm wondering about the best method to incorporate in a signup form a
> Terms and Conditions agreement, which being so long will be bought to
> the page externally. Or if it's thought best, maybe not!
> On a previous occasion I went forward using the <object> tag. The
> advantage to my mind is that, my document (that may change in future)
> is separate to the form and for those who don't have a browser capable
> of using the <object> tag, can see alternative text to link to the
> separately hosted T&C page.
> But it's been put to me at work, there might be a way to house the
> document in a div, give the div a fixed size and make it scrollable.
> Alternatively I could use a textarea element, although I'm given to
> understand it would need to be outside the <form> so as not include it
> in the 'Signup' event when the submit button is clicked. However to
> satisfy the designer, who follows that the convention is that the form
> is visually seen before the last submit button, I'd use CSS to
> position it - but that doesn't sound very semantic to me?
> Putting it on another page, that you would link to, read, then return
> to the form to agree to has been rejected for the sanctity of the
> concept of a single page signup document.
> I hope I've been clear, and I guess I'm interested in anything similar
> to this in best practice, accessibility and standards.
> Cheers for just being there folks,
> John Unsworth
Hi John,
I haven't ever needed to write this before, but I have seen a decent
sized scroll box at the bottom of a form with a check box to confirm
they have read it and agree to it.
All the ones I have seen are above the final submit button, but I'm
not sure if they are truly inside the form or not.
Depending on how you are submitting the form, and how big of a file
the T&C page is, you COULD submit it and just ignore it... But
depending on the load of the server it might take a little bit longer
to process the form.
Just something to think about :)
--
Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
11287 James St
Holland, MI 49424
www.raoset.com
[EMAIL PROTECTED]
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
