- From: david poehlman <david.poehlman@handsontechnologeyes.com>
- Date: Sat, 28 Aug 2004 14:38:04 -0400
- To: "Joe Clark" <joeclark@joeclark.org>, "WAI-IG" <w3c-wai-ig@w3.org>
from my experience and from my work on the uaawg, Jaws is not a user agent. A user agent in and of its self renders web content. Try rendering an html file with out a user agent using jaws and it might come up in notepad but you'd get the raw data. It might come up in word pad but you would get raw data. It might show up in word, but there is no guarantee that it would be accessible, but oh, that rub again, there is something else doing the rendering. We need to be real clear on what is and what is not a user agent here lest we stumble over our feet think ing that we can code for jaws and our work is done. Johnnie Apple Seed ----- Original Message ----- From: "Joe Clark" <joeclark@joeclark.org> To: "WAI-IG" <w3c-wai-ig@w3.org> Sent: Saturday, August 28, 2004 2:15 PM Subject: Re: Layout versus data tables proposal for null summary attribute > Jaws retrieves nothing, It renders nothing. An exective from Freedom Scientific explicitly denied that claim. It relies on IE for rendering *and does its own rendering* and calculation. > The guidelines were written to > take a wide array of combinations into account so what 2 really means is > that jaws together with a user agent is a user agent. Jaws together with a browser are *two* user agents. -- Joe Clark | joeclark@joeclark.org Accessibility <http://joeclark.org/access/> Expect criticism if you top-post
Received on Saturday, 28 August 2004 18:37:24 UTC