| Bad
HTML |
If
your HTML is malformed, the browser will do its best and at times
quit processing your file.
This shouldn't happen if you use FrontPage or another reputable
HTML editor.
This category includes any scripts (JavaScript, CGI, etc) that
you use in your site.
|
|
| Broken
hyperlinks |
Links
that don't work are a no-no... especially if they are links to
your own pages.
You may link to an external site that disappears, so your
hyperlinks will require a certain amount of maintenance.
|
|
| Unreadable
text |
If
the text does not sufficiently contrast with the background, then
how can the page be used?
This rule applies to general text in the page, buttons or any
other graphics including text.
|
|
| Bad
image size |
Don't
make your images too big to be viewed on a computer display, or
too small to discern the content of the image.
There are some exceptions to this... if you warn the user that
an extremely large image is coming because it is required for your
application, then that's fine.
|
|
| Too
long to download |
This
is a case of user notification. If any page on your site will take
a typical user (currently, someone with a 56Kb modem) an
inordinate amount of time to download, then the user should be
warned ahead of time.
Again, if your application calls for the downloading of large
files, that's fine. Warn the user of the size and/or expected time
of the download.
|
|
| Misspelled
words |
Spell-check
your pages.
This is supplied by FrontPage and most other web page editors.
|
|
| Support
common browsers |
Your
page should be viewable on the most popular browsers: Microsoft
and Netscape
|
|
| |
