You will get a more useful critique if you follow these suggestions
BEFORE submitting your site here:

- Learn HTML (and CSS, if you plan to use it). That may seem obvious,
but even if you plan to use a spiffy HTML generator, you won't be able
to understand the output from the next step (or most of the replies you
receive here) unless you can at least READ both languages. And, frankly,
most generators don't do a very good job; you can do better. You can
start at http://www.w3schools.com/.

- Start each of your pages with a DOCTYPE, so browsers (and validators,
see the next item) know which version of HTML you are using. Otherwise
it may be not be interpreted as you expect. For new pages, use the
DOCTYPE for HTML 4.01 STRICT. See
http://www.w3.org/TR/html4/struct/g...ml#version-info for the
syntax to use.

- Validate your HTML (and CSS, if you use it). Although your site may
'look' OK to you, using one environment, incorrect HTML or CSS can make
it look very different in other environments. Since you can't control
the user's environment, your best bet is to start with strictly valid code.

- To validate HTML, go to http://validator.w3.org/.
- To validate CSS, go to http://jigsaw.w3.org/css-validator/.

- Either don't specify any font-size at all, or specify it using
percent values from 90% upward, with 100% for most of your text. 100%
means the browser renders the text in its default size, and many users
have set this to their preferred size, sometimes for disability reasons.
Be particularly careful when using Verdana, which appears larger than
most other fonts at a given size value; default text may be
significantly smaller. See
http://www.xs4all.nl/~sbpoley/webmatters/verdana.html.

- Always put appropriate alt= text on your <img> tags. Appropriate
means something that will perform the function of the image if it can't
be displayed or if the user can't see it. Use alt="" if the image is
merely decorative.

- If you have a table of data, by all means, use the <table> tag family
to present it on your page. AVOID using these tags just to position
unrelated data on the page. Instead, use CSS.  [NOTE: There is much
emotional debate about this suggestion; you will never get in trouble by
following it, but ignoring it could cause lengthy chains of responses
which will be of little help to you.]

- Make sure your site functions as desired with JavaScript disabled,
since some users don't have it.

- Test your site at several screen areas and window sizes. Many users,
especially those with large high-resolution displays, run with the
browser at less than full-screen size. Some here suggest that browser
sizes down to 400px wide are used (allowing for a second application to
run alongside, for example). Certainly your site should not have
horizontal scrollbars when the browser is at 800px wide.

- Expect most of the critique responses to address HTML coding issues
(that's the name of the newsgroup, after all), along with cross-browser
compatibility, accessibility, and the user interface. Artistic
considerations will typically be the LAST thing to be addressed. Do not
be surprised if you see emotional reactions to your work, or if side
discussions or arguments begin. Usenet is, after all, a place for
discussion. If someone replies strongly, it's likely because many others
make the same error, and they are a bit tired of it. It is certainly not
personal. Remember, the regulars are here in their free time, this is
not a "help desk". If someone seems a bit over the top, still accept
their critique at face value.

- Finally, if any critique leaves you confused, feel free to ask. Reply
to that person's post, snip out all but the person's name and the
part(s) you are replying to, and BELOW that ask the question.
Top-posters and no-snippers are generally less likely to get meaningful
answers than those who take care to put their posts in a more readable
style. See posts by regulars in this newsgroup for examples if this is
not clear.

Chris Beall, with help from many others at alt.html.critique