- From: Charles McCathieNevile <charlesn@srl.rmit.EDU.AU>
- Date: Thu, 19 Nov 1998 16:53:45 +1100 (EST)
- To: "Charles (Chuck) Oppermann" <chuckop@microsoft.com>
- cc: WAI UA group <w3c-wai-ua@w3.org>
Good. So here is the sort of low-hanging fruit we are looking for, right? I suspect (and hope) that it is a fairly trivial extension of the approach to test for attributes, in the same way as CSS2 requires What I am thinking is that this approach can be applied to the very simplistic sort of table navigation (cell by cell or row by row, without context) that I discussed earlier. It could also solve (for example) the problem of the PAGL group about skipping over links which are in blocks. The nature of the element, and such attributes as TITLE or ALT could be used to provide some meaningful feedback about the structure which is being walked. It does not solve the problem of where the heck am I - for tables you need a special beastie to run the algorithm that is used by people looking at a table to provide that information, which is (I think) also important to navigating a table. Then I get into idler speculation - is this a technique for building configurable outlines, or does the process go the other way around? And so forth. Charles McCathieNevile On Wed, 18 Nov 1998, Charles (Chuck) Oppermann wrote: > Extremely easy to do. Here's a sample JavaScript to do display the name of > the HTML tag for each element: > > for (var i = 0, i < document.all.length, i++) > alert(document.all.item(i).tagName); > > This is taken from page 169 of the book "Dynamic HTML" by Scott Issacs. > > Charles Oppermann > Program Manager, Accessibility and Disabilities Group, > Microsoft Corporation > mailto:chuckop@microsoft.com http://microsoft.com/enable/ > "A computer on every desk and in every home, usable by everyone!" > >
Received on Thursday, 19 November 1998 00:57:49 UTC