[Chris, how does this seem to you?]
I’ve spoken to our web accessibility expert and he has the following
comments:
Gecko: Lose the position: fixed; stuff. It’s still a nightmare to
use. Use position: absolute; instead. (Will also better work in IE)Make it work at reasonable resolutions - I’m running at 831px wide
and it doesn’t fit.Get rid of the font sizes set in px - they won’t rescale in IE, and
not particularly well in anything else. Use caution with font sizes
<100% (80% is likely to be unreadable in some situations, 90%
should be okay but not for paragraphs of text)Opera: The horizontal scrolling doesn’t happen, the stuff that
would generate a horizontal scrollbar just goes off the right of
the screen. (Opera is available for Linux for testing)IE6/Win: I can’t see the login box. This suggests that the rest of
the stylesheet will be badly messed up too. (After using the
keyboard navigation and a bit of guesswork, managed to log in
anyway. The top half of the layout is in pieces, the main area and
footer is okay but is also about a screen height down the page…(A single windows box isn’t that expensive for testing and can have
IE 5, 5.5 and 6 co-installed on it. Trying to debug IE CSS layout
via second-hand reports of what looks wrong is near-impossible and
will take weeks.)IE 5 on the Mac is likely to have similar problems due to position:
fixed.W3M/Lynx: Page fails to display. Problem caused by <!–[if lt IE
7]> in the , which Lynx, and indeed anything else (other than
IE), will interpret as an unclosed comment. I don’t know why
Gecko/KHTML don’t interpret this as an unclosed comment, probably
a bug in their parsers.Anything: The close buttons on the various bits of the homepage are
Javascript dependent. Ideally they should do something server-side
to hide those bits, but you should use JS to write the close buttons
out so that non-JS browsers don’t see them.
Andrew Stribblehill
Systems programmer, IT Service