- From: Aaron Smith <aaron@gwmicro.com>
- Date: Mon, 02 Jul 2001 08:21:57 -0500
- To: "David Poehlman" <poehlman1@home.com>, "Ian B. Jacobs" <ij@w3.org>, <w3c-wai-ua@w3.org>
This is going to be the case for most screen readers. I can only speak for Window-Eyes, but we do not parse HTML ourselves. Instead, we receive the parsed information from the browser through MSAA. So, if the TAGs in question are supported by MSAA, then they will be supported by Window-Eyes. If we have to step around MSAA and go right to the DOM to get some feature to work, then we will. But those cases are usually rare. At 07:29 PM 6/26/2001 -0400, David Poehlman wrote: >I'd like to see that one my self. I think part of it has to do with how >msaa and the browsers support the elements. part for instance of the >way jfw handles the title tag has to do with the current implementation >of it by ie. > >----- Original Message ----- >From: "Ian B. Jacobs" <ij@w3.org> >To: <w3c-wai-ua@w3.org> >Sent: Tuesday, June 26, 2001 5:54 PM >Subject: Information about screen reader support for HTML >elements/attributes? > > >Hi folks, > >Does anyone know where I can find matrices of which >screen readers support which HTML attributes and elements >that are beneficial to accessibility (e.g., abbr)? > >Thanks for any pointers. > > - Ian > >-- >Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs >Tel: +1 831 457-2842 >Cell: +1 917 450-8783 -- Aaron Smith GW Micro Phone: 219/489-3671 Fax: 219/489-2608 WWW: http://www.gwmicro.com FTP: ftp://ftp.gwmicro.com Technical Support & Web Development
Received on Monday, 2 July 2001 09:22:04 UTC