- From: Al Gilman <asgilman@iamdigex.net>
- Date: Wed, 03 Mar 1999 15:29:13 -0500
- To: Marja-Riitta Koivunen <marja@w3.org>, w3c-wai-ua@w3.org
What you describe is the systematic, structured programming way to describe the capability. Find [next] instance matching <pattern>. Where pattern includes both content and context qualifiers (context includes HTML element names and attribute values, c.f. selectors in CSS). Have you played with the Lynx functions? They are pretty simple but there is some adjustment of what class of elements is numbered, and then there is both incremental and absolute motion within that class. [Incremental motion over a default class even when nothing is numbered] This is of enough interest so that this functionality is still growing. Al At 01:58 PM 3/3/99 -0500, Marja-Riitta Koivunen wrote: >Could the tabbing among different kind of elements be defined similar to a >"find" and "find next" dialog box (in accessible way). In addition to the >text string, the user could select which element types are searched e.g. >header, table, paragraph, table cell, a named element. > >The user could then define some of the most useful searches to be in a >separate list easily available to users e.g. when alt tab is pressed. > >Can this be done in an easily accessible way? > > Marja >
Received on Wednesday, 3 March 1999 15:26:27 UTC