- From: Charles (Chuck) Oppermann <chuckop@MICROSOFT.com>
- Date: Mon, 16 Nov 1998 12:35:49 -0800
- To: Kathy Hewitt <kathyhe@MICROSOFT.com>, "'Scott Luebking'" <phoenixl@netcom.com>, w3c-wai-ua@w3.org
I agree with Kathy - some folks should try working with the technology available. For over a year now, WinVision 97 has made tables highly accessible through Active Accessibility. They even have a bunch of tables in their web site to prove their point. JFW uses a technique to manipulate the document to unroll the table horizonatally. Tell me why this absolutely must be in the browser code. -----Original Message----- From: Kathy Hewitt [mailto:kathyhe@microsoft.com] Sent: Monday, November 16, 1998 11:17 AM To: 'Scott Luebking'; w3c-wai-ua@w3.org Subject: RE: A table navigation technique I don't the see why that has to be a priority 1. If a browser doesn't have this option, does it make it inaccessible? -----Original Message----- From: Scott Luebking [mailto:phoenixl@netcom.com] Sent: Sunday, November 15, 1998 1:30 PM To: w3c-wai-ua@w3.org Subject: Re: A table navigation technique Hi, I was wondering if there are any objections to the guidelines assigning first priority level to visual browsers' providing the option of tables being directly rendered by the browsers in serialized format with the table cell identification approach? Scott
Received on Monday, 16 November 1998 15:35:54 UTC