 | Users should be able to quickly look at each link and tell where it goes. | Usability.gov 10:1 , | , |
|
Don't use generic link labels like "click here" or "read more" because they're hard to tell apart when users scan a page.
| | |
| Link text:
"Read more" file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 141 ,185 ,205 ,232 ,252 ,
...
|
 | Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load. | Usability.gov 14:3 , | , |
|
This makes the page very hard to read while it's loading.
Add width and height attributes to the img tag matching the image dimensions. Authoring tools
like Dreamweaver can automate this process. | | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 58 ,247 ,262 ,285 ,329 ,
...
|
 | Use background images sparingly and make sure they are simple, especially behind text. | Usability.gov 14:1 , | , |
|
Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates.
| | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox_elemei/css_f56a53686dc83cefceee43887540f874.css, | | 12 ,12 ,12 ,34 ,34 ,
...
|
 | Use text links rather than image links. In general, text links are more easily recognized as clickable. | Usability.gov 10:6 , | , |
|
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image.
Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping').
Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options. | | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 433 , |
 | Create data entry fields that are large enough to show all of the entered data without scrolling. One study has shown that search fields should be at least 35-40 characters long to accommodate 95% percent of search terms. | Usability.gov 13:8 , | , |
|
Make sure each search field holds at least 35 characters, which should accommodate 95% of search terms.
| | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 77 , |
 | Use at least a 12-point font on all Web pages. | Usability.gov 11:8 , | , |
|
The following are all smaller than 12 point:
- <p style="font-size: 11pt;" >
- <p style="font-size: 11px;" >
- <p style="font-size: small;" >
- <font size="2" >
- <font size="-1" >
For users over age 65, it may be better to use at least fourteen-point fonts.
Never use less than nine-point font on a Web site.
| | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox_elemei/css_dde172d40cb47b44b19e64699d917baf.css, | | 3 , |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox_elemei/css_f56a53686dc83cefceee43887540f874.css, | | 92 , |
 | Use headings in the appropriate HTML order (don't put H1 inside an H2, or H2 inside H3 etc.) | Usability.gov 9:7 , | , |
|
Using the appropriate HTML heading order helps users get a sense of the hierarchy of information on the page. The appropriate use of H1-H3 heading tags also allows users of assistive technologies to understand the hierarchy of information.
| | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 33 , |
 | Use link text between 3 and 80 characters so it's long enough to be understood, but avoids line wrapping. | Usability.gov 10:11 , | , |
|
A single word text link may not give enough information about the link's destination. A link that is a full sentence is difficult to read quickly, particularly if it wraps to another line.
| | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 127 , |
 | Capitalize the first letter of the first word in lists. | Usability.gov 12:9 , | , |
|
Only the first letter of the first word should be capitalized unless the item contains another word that would normally be capitalized.
| | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 65 ,142 ,186 ,233 ,253 ,
...
|
 | Make sure one radio button in a radio button group is always selected. If users can choose not to activate any of the radio button choices, provide a choice labeled 'None'. | Usability.gov 13:23 , | , |
| | | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 161 ,165 ,169 ,297 ,301 ,
...
|
 | Use site maps for Web sites that have many pages. | Usability.gov 7:10 , | , |
|
Site maps provide an overview of the Web site. They may display the hierarchy of the Web site, may be designed to resemble a traditional table of contents, or may be a simple index.
You can add a site map with a tool like PowerMapper.
| | |
| file://C:/Documents and Settings/Bana/Asztal/faszom/Drupal 7.0 Alpha3 Accessibility Testing Sandbox.htm, | | 1 , |
 | 12 issues on 3 pages
|