In message <ekogn0ti4t8sqr711l37oe1nijeroh9jha (AT) 4ax (DOT) com>, Randall Fox
<fox_no_spam-usenet001 (AT) yahoo (DOT) com> writes
Overall -- a nice looking site.
Some suggestions:
(a) Check the images and ensure that there's adequate 'alternative text'
specified for all of them. On the first page there's no alt. text for
the logo; more importantly you've got no alt text on 2 links
(assets/xml.gif).
Complete and correct alternative text is especially important when users
with Assistive Technology (AT) UAs (screen-readers, talking browsers,
etc.) are 'reading' the site.
(b) Put a 'skip navigation' link as the first entry on each page in
order to bypass the navigation and go directly to the content. The link
can be made invisible.
(c) You have many headings that are styled as such visually (features,
requirements, news, etc.) but which are not in the HTML mark-up. i.e. no
<h1> <h2> <h3> etc.
Headings are important for AT users.
(d) The <title></title> on each page contents should reflect the purpose
of that page.
(e) As others have said, there are problems with MSIE when trying to
resize text due ti the use of pt and px. While you're figuring that one
out, you might consider removing the 'line-height' from the CSS as
people will be able to resize text in IE happily using the
'accessibility' option; the text resizes OK, but the fixed leading will
make the headings difficult to read.
Another good reason for not using px or pt in the line-height is that
some browsers (such as Opera) can be configured so that the text size is
automatically set to a minimum size. A fixed leading (line-height) can
make the affected text hard/impossible to read.
(f) On the FAQ page, it would be useful to mark-up the questions as
headers (<h2> or whatever) to aid navigation for AT users. i.e They can
skip from header-to-header without having to wade through the FAQ menu
to find the next link.
regards.
--
Jake