Electronic Books

WHAT'S HOT
PARTS:
Part 4
Part 5
Part 6
Part 7
Part 8
Part 9
Part 10
Part 11
Part 12
Part 13
Part 14
Part 15
Part 16
Part 17
Part 18
Part 19
Part 20
Part 21
Part 22
Part 23
  • Partners
Prev | Current Page 143 | Next

Kevin Potts

"Web Design and Marketing Solutions for Business Websites"

gif" ??
alt="Submit Query" />
This ensures that the user??”whether on a standard browser or a screen reader??”knows
exactly what will happen when the button is clicked. As a general rule of thumb, never use
standard links to submit form content, as they are not proper form controls and might
be ignored by screen readers.
Clearly label required fields. Many forms require that certain fields contain content before
the form can be submitted. These are usually things like name, e-mail, message, and so
forth. There is nothing inherently wrong about this, but the design of the form must
clearly communicate exactly which fields are required and which ones are optional.
Designers need to not only indicate which ones are required, but also explain how they??™re
indicating that. For instance, it is common practice to add a small character or icon next to
the label of an obligatory field, like an asterisk. However, somewhere near the form, there
needs to be a small key explaining exactly what the asterisk indicates (see Figure 3-5 for an
example). Also keep in mind that color alone should not be used to denote a required
field; as we explored earlier in this chapter, some color combinations are impossible to tell
apart by those with certain types of visual impairment.


Pages:
131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155
Inside LightWave v9 (page 1405) Pro SQL Server Disaster Recovery (page 105) Tapestry 5: Building Web Applications (page 323)