<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Web Design&gt;Forms</title>	<link>http://tc.eserver.org/dir/Articles/Web-Design/Forms</link>
	<description>A listing of the most recently indexed works about Articles and Web Design and Forms in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Web Design&gt;Forms</title>
		<link>http://tc.eserver.org/dir/Articles/Web-Design/Forms</link>
	</image>
	<item>
		<title>Strategies on How To Motivate Users to Sign Up Through Design</title>
		<link>http://tc.eserver.org/35705.html</link>
		<guid>http://tc.eserver.org/35705.html</guid>
		<description>Be it web-based applications or online services, they are taking the Internet by storm. Many websites introducing these services are created and launched to get users to sign up and use the software (hopefully for a long-term). The question is: How do we get users from the unfamiliar zone into the interested zone and subsequently becoming a first time use?</description>
	</item>
	<item>
		<title>(Almost) Never Add a Reset Button to a Form</title>
		<link>http://tc.eserver.org/35397.html</link>
		<guid>http://tc.eserver.org/35397.html</guid>
		<description>Next time you consider adding a reset button to a form, think it through very carefully first. Does the user really benefit from being able to reset the form? Is being able to reset the form to its initial state so valuable that it is worth the risk of the user losing the data they have entered? Probably not.</description>
	</item>
	<item>
		<title>Inline Validation in Web Forms</title>
		<link>http://tc.eserver.org/35168.html</link>
		<guid>http://tc.eserver.org/35168.html</guid>
		<description>Inline validation gives people several types of real-time feedback: It can confirm an appropriate answer, suggest valid answers, and provide regular updates to help people stay within necessary limits. These bits of feedback can be presented before, during and / or after users provide answers.</description>
	</item>
	<item>
		<title>Accessible HTML/XHTML Forms</title>
		<link>http://tc.eserver.org/34001.html</link>
		<guid>http://tc.eserver.org/34001.html</guid>
		<description>Forms are often the most tricky aspect of web development for beginners to get their head around, largely because it means stepping out of the comfort zone of one-way information - no longer are you simply presenting information at the person viewing your site, now you are asking for input, for feedback that you have to process in some way. And just as it may be difficult for HTML beginners to understand just how they handle form data, so is it difficult to understand some of the issues relating to accessibility.</description>
	</item>
	<item>
		<title>Designing a Login Form</title>
		<link>http://tc.eserver.org/33381.html</link>
		<guid>http://tc.eserver.org/33381.html</guid>
		<description>Over at Smiley Cat Web Design they’ve put together a showcase of many different login and registration forms. While you’re there, take a look at some of the other showcases listed in the sidebar. They have sets for calendars and date pickers, footers, search boxes, and many more.</description>
	</item>
	<item>
		<title>Five Ways To Make Sure That Users Abandon Your Forms</title>
		<link>http://tc.eserver.org/33123.html</link>
		<guid>http://tc.eserver.org/33123.html</guid>
		<description>What do you really need to know in your form process? Be brutal. Don&apos;t include stuff that your sales team would like. Completing a form is rarely (if ever) the goal in and of itself. The goal is to entice the user into a deeper relationship (of some sort) with your web site. Notice that I didn&apos;t say that the goal was to complete a transaction or make a sale. That is evidence of the deeper relationship, not the vehicle by which you persuade your users.</description>
	</item>
	<item>
		<title>Accessible CSS Forms: Using CSS to Create a Two-Column Layout</title>
		<link>http://tc.eserver.org/33124.html</link>
		<guid>http://tc.eserver.org/33124.html</guid>
		<description>Websites have become less accessible and more complex over time according to recent studies. Learn how to buck the trend by creating fast, accessible CSS forms that work with modern browsers and gracefully degrade.</description>
	</item>
	<item>
		<title>Accessible Forms</title>
		<link>http://tc.eserver.org/33131.html</link>
		<guid>http://tc.eserver.org/33131.html</guid>
		<description>This document is concerned with what the user of a Website form &quot;sees&quot; and interacts with. It outlines how you can create forms for the Web that are more accessible and describes the appropriate use of.</description>
	</item>
	<item>
		<title>Build Accessible Online Forms</title>
		<link>http://tc.eserver.org/33132.html</link>
		<guid>http://tc.eserver.org/33132.html</guid>
		<description>Ask anyone who has had to fix a Website that&apos;s littered with accessibility howlers, and top-most in their list of problems encountered will be forms, closely followed by tables. These two topics always seem to present the most difficulties, but they needn&apos;t be a problem. For the most part, forms are a problem because the extra accessibility tags are simply not known to the Web designer -- after all, it looks right, it seems to work... what&apos;s the problem? Only by switching off the monitor and using a screen-reader can our oblivious Web developer understand the issues.</description>
	</item>
	<item>
		<title>Colons at the End of Labels?</title>
		<link>http://tc.eserver.org/33133.html</link>
		<guid>http://tc.eserver.org/33133.html</guid>
		<description>You are writing captions or labels for fields in forms, for example &apos;Name&apos; or &apos;Date of birth&apos;. Should they be finished with a colon, or not?</description>
	</item>
	<item>
		<title>Creating Bulletproof and Easy to Complete Web Forms</title>
		<link>http://tc.eserver.org/33134.html</link>
		<guid>http://tc.eserver.org/33134.html</guid>
		<description>Effective form design is a great way to boost conversion rates. Jason Fried and Matthew Linderman share with us the secret of how to create attractive and functional forms.</description>
	</item>
	<item>
		<title>Forms: The Importance of Getting it Right</title>
		<link>http://tc.eserver.org/33135.html</link>
		<guid>http://tc.eserver.org/33135.html</guid>
		<description>Urgh – it’s what we all think when presented with a form to complete, whether printed or online. What is it about forms that make us feel this way? Maybe, the history of being officious and complicated, a drain on our time, and they often make us feel stressed. As forms represent a business or an organisation, all these feelings are subsequently associated with that organisation – not good for customer relations or reputation!</description>
	</item>
	<item>
		<title>Nailing Form Layout</title>
		<link>http://tc.eserver.org/32751.html</link>
		<guid>http://tc.eserver.org/32751.html</guid>
		<description>You may not realize it, but there are times when each variant of form layout can have a positive or negative impact on how the form (and your site) is used or perceived. And applying the right variant at the right time is one of the simplest things you can do to improve your user’s experiences.</description>
	</item>
	<item>
		<title>Fancy Form Design Using CSS</title>
		<link>http://tc.eserver.org/32660.html</link>
		<guid>http://tc.eserver.org/32660.html</guid>
		<description>Forms. Is there any other word that strikes as much fear into the hearts of grown web designers? There&apos;s also an improperly held belief that the only way you can guarantee that a form displays properly is by using tables. All of the code reproduced here for forms is standards-based, semantic markup, so you&apos;ve got no excuse for relying on tables now!</description>
	</item>
	<item>
		<title>Improve Your Forms Using HTML 5!</title>
		<link>http://tc.eserver.org/32551.html</link>
		<guid>http://tc.eserver.org/32551.html</guid>
		<description>HTML hasn&apos;t really been updated since HTML version 4 was released back in 1998. However, the WHATWG community has been working on HTML since 2004 and this will hopefully result in some much needed improvements. This article shows some of the new functionality of the proposed form chapter of HTML5: Web Forms 2.</description>
	</item>
	<item>
		<title>Formal Weirdness</title>
		<link>http://tc.eserver.org/32498.html</link>
		<guid>http://tc.eserver.org/32498.html</guid>
		<description>Explains some of the technical reasons for form controls being so hard to style consistently across platforms with CSS. Also asks a lot of good questions related to how various CSS properties should affect form controls if browsers would let them.</description>
	</item>
	<item>
		<title>Multiple Form Labels and Screen Readers</title>
		<link>http://tc.eserver.org/32425.html</link>
		<guid>http://tc.eserver.org/32425.html</guid>
		<description>Just about every website needs some forms. Sometimes there are many of them, sometimes just a single contact form. Regardless of their number, they need to be usable and accessible, which can sometimes be a little more work than it would be if theory and practice aligned a little better.</description>
	</item>
	<item>
		<title>Use the Label Element to Make Your HTML Forms Accessible</title>
		<link>http://tc.eserver.org/32453.html</link>
		<guid>http://tc.eserver.org/32453.html</guid>
		<description>There are plenty of articles and tutorials that describe how to create accessible HTML forms out there. Despite that it is common to come across forms that do not use a single label element and forms that use label elements but do so incorrectly.</description>
	</item>
	<item>
		<title>Autopopulating Text Input Fields with JavaScript</title>
		<link>http://tc.eserver.org/32460.html</link>
		<guid>http://tc.eserver.org/32460.html</guid>
		<description>Few people will argue against the need to explain to users what they are supposed to enter into text input fields. One common workaround when no label can be displayed is to put some placeholder text in the text field and let that act as the label.This approach works reasonably well, but it burdens the user with having to clear the input before entering their own text, which can lead to frustration and mistakes. An approach that avoids that is using JavaScript to clear the input when it receives focus. Since that won’t work when JavaScript support is missing, JavaScript should be used to insert the placeholder text as well.</description>
	</item>
	<item>
		<title>Spruce Up Your Search Box with CSS and a Background Image</title>
		<link>http://tc.eserver.org/32473.html</link>
		<guid>http://tc.eserver.org/32473.html</guid>
		<description>Very few designers appreciate the aesthetic of a text input field, and styling form fields cross-browser on any Web site can be a tedious and frustrating experience. The compromise typically involves applying a simple colored border and background to the fields. I think this is the right approach for Web sites and applications that are form field intensive, but the search box plays a special role in the design, and it deserves a little more attention.</description>
	</item>
	<item>
		<title>Getting a Form&apos;s Structure Right: Designing Usable Online Email Applications</title>
		<link>http://tc.eserver.org/32379.html</link>
		<guid>http://tc.eserver.org/32379.html</guid>
		<description>There are a million websites out there. There are a million email service providers out there. How do you ensure that you gain the right audience to join your service? What are those factors that will help users move ahead and become your loyal customer? Part of the answer has to do with the first step: Registration!</description>
	</item>
	<item>
		<title>Creating Killer Forms with CSS</title>
		<link>http://tc.eserver.org/32076.html</link>
		<guid>http://tc.eserver.org/32076.html</guid>
		<description>So you’ve been to about a million websites at this point in your cyber life. There’s a little bit of everything in the online jungle, with every different imaginable style, color, and layout. Everyone is trying to be different, trying to separate themselves from the pack. So why is it that nearly every website, from the coolest of the cool to the worst of the worst, seem to still be using the same, ugly form fields that are default.&#xD;&#xD;Well, that’s about to change, at least on your website. I’m going to give you some quick and easy tips to spice up your form fields and set your website apart from the rest.</description>
	</item>
	<item>
		<title>Streamline Your Forms with Widgets</title>
		<link>http://tc.eserver.org/31955.html</link>
		<guid>http://tc.eserver.org/31955.html</guid>
		<description>“Advanced forms” are rarely that. A more fitting name would be “Overwhelming and confusing forms”. But with Jason Long’s clever approach to streamlining a screen full of checkboxes, you might just be able to once again look fondly on your forms.</description>
	</item>
	<item>
		<title>Calling in the Big Guns: Review of Web Form Design: Filling in the Blanks</title>
		<link>http://tc.eserver.org/31829.html</link>
		<guid>http://tc.eserver.org/31829.html</guid>
		<description>What is likely to win the most converts is the joy Wroblewski takes in designing. This impression becomes clear as you page through the book. He isn’t just an ardent evangelizer, following the rituals of going to conferences selling snake oil. He’s been there in the trenches, just like you; he’s done this a hundred, maybe a thousand times. He’s tested these ideas and provides a framework for you to use from day one. Half the battle in good form design is defending your decisions to stakeholders.</description>
	</item>
	<item>
		<title>Sign Up Forms Must Die</title>
		<link>http://tc.eserver.org/31072.html</link>
		<guid>http://tc.eserver.org/31072.html</guid>
		<description>You load a new web service, eager to dive in and start engaging, and what&apos;s the first thing that greets you? A sign-up form. We can do better, says Luke Wroblewski, author of Web Form Design: Filling in the Blanks. Via a technique of &quot;gradual engagment,&quot; we can get people using and caring about our web services instead of frustrating them (or sending them to a competitor&apos;s site) by forcing them to fill out a sign-up form first.</description>
	</item>
	<item>
		<title>Selection-Dependent Inputs</title>
		<link>http://tc.eserver.org/28659.html</link>
		<guid>http://tc.eserver.org/28659.html</guid>
		<description>Successful Web applications tend to grow--both in terms of capability and complexity. And this increasing complexity is often passed on to and absorbed by a Web application&apos;s forms. In addition to needing more input fields, labels, and Help text, forms with a growing number of options may also require selection-dependent inputs.</description>
	</item>
	<item>
		<title>Evaluating Forms</title>
		<link>http://tc.eserver.org/27482.html</link>
		<guid>http://tc.eserver.org/27482.html</guid>
		<description>To demonstrate an example of some accessibility issues in HTML Forms, the following content intentionally has accessibility errors.</description>
	</item>
	<item>
		<title>Forms vs. Applications</title>
		<link>http://tc.eserver.org/26634.html</link>
		<guid>http://tc.eserver.org/26634.html</guid>
		<description>Once an online form goes beyond two screenfulls, it&apos;s often a sign that the underlying functionality is better supported by an application, which offers a more interactive user experience.</description>
	</item>
	<item>
		<title>Dynamically Filtering Dropdown Lists in JavaScript</title>
		<link>http://tc.eserver.org/26330.html</link>
		<guid>http://tc.eserver.org/26330.html</guid>
		<description>This article describes a technique that takes input from a form text field and uses it to bring matching options to the top in a dropdown list.</description>
	</item>
	<item>
		<title>Dysfunctional Forms Syndrome</title>
		<link>http://tc.eserver.org/24552.html</link>
		<guid>http://tc.eserver.org/24552.html</guid>
		<description>Prevent major user annoyance by checking all your web forms: feedback, comment posting, product orders, newsletter sign-up, newsletter opt-in, unsubscribe option, site registration, etc. When a form won&apos;t submit, or otherwise fails, after user inputs lots of data, it causes extreme ill will toward your web site, and may be legal violation (UCE laws).</description>
	</item>
	<item>
		<title>Developing an Online Form</title>
		<link>http://tc.eserver.org/20643.html</link>
		<guid>http://tc.eserver.org/20643.html</guid>
		<description>Creating an online form can present developers with many challenges. This case study reviews how a paper-based form was taken through the usability engineering process to develop a functional online version. We discuss the steps in planning and research, prototype development, test design, and the usability test results.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Web-Design/Forms.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>