W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2000

RE: JAWS discards SPAN content?

From: David Holstius <holstius@pilot.msu.edu>
Date: Tue, 5 Dec 2000 22:21:04 -0500
To: "'W3c-Wai-Ig@W3.Org'" <w3c-wai-ig@w3.org>
Message-ID: <BJEMLNACJIHFHFJPLFCJOECFCAAA.holstius@pilot.msu.edu>

The page now validates as XHTML and the LABEL tags now reference the "id"
attribute of the INPUT tags. Thanks to David Wooley for catching this. I'd
originally thought the page validated, but it was part of a site that
required a login, and when the validator tried to parse this page, it was
kicked out to the login and thus actually validated the *login* page.

Re: Netscape performance. This page was part of a demo project I was
presenting to an IE audience. The project is on hold and won't be public for
some time. I haven't tested in in NS6/Mozilla yet. Typically, for a public
version, I'd install a sniffer of some sort and feed different stylesheets
to CSS-compatible browsers than to (shudder) NS 4.x. I use a "positive-id"
scheme, i.e. I'll take the base page, add whatever valid CSS I know won't
break in NS4, and feed that as default to all browsers. Then (using
server-side if available, otherwise some JS) I additionally feed the rest of
the CSS I want to use, but ONLY for those browsers I have managed to
personally test it on, before the page goes out the door. So untested
browsers just get the base level CSS, but sometimes I do add a third
stylesheet for NS4.

Re: Accesskeys. Again, the page was for a known audience, but I know now
that those accesskeys in the form will interfere with (at least) IBM Home
Page Reader's defaults, thanks to Jim Thatcher. I agree; using this many
accesskeys is probably not a good idea  but I wanted to emphasize the
concept to my demo audience.

David Holstius
Received on Tuesday, 5 December 2000 22:19:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:10 UTC