W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2000

Re: Checkpoints 7.5, 2.5, 2.6, 1.5, 3.8

From: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
Date: Tue, 29 Aug 2000 08:26:46 -0500
Message-Id: <4.3.1.2.20000829082541.013a76c8@staff.uiuc.edu>
To: "Hansen, Eric" <ehansen@ets.org>
Cc: w3c-wai-ua@w3.org
Eric,
I agree with Ian.  I don't think there is any reason to mention a 
particular rendering technology in checkpoint 7.5.

Jon

At 07:02 PM 8/28/2000 -0400, Ian Jacobs wrote:
>"Hansen, Eric" wrote:
> >
> > To: UA List
> > From: Eric Hansen
> > Re: Checkpoints 7.5, 2.5, 2.6, 1.5, 3.8
> >
> > This memo concerns Ian's memo [2] (Re: Proposal for 7.5 [Was Re: Issue with
> > checkpoint 7.5 (search) and serial...) and relates to other memos.
> >
> > ====
> >
> > Suggestion 2: Refine checkpoint 7.5.
> >
> > As for your revised wording for checkpoint 7.5, it seems to be OK but might
> > bear some refinement.
> >
> > IJ:
> > > Proposal, based on Eric's text:
> > >
> > > <NEW BY IAN>
> > > 7.5 Allow the user to search through text that has been rendered.
> > >     The search must encompass all text within the
> > >     viewport, both inside and outside the point of regard. Allow the
> > >     user to start a forward search from a location in content
> > > selected
> > >     or focused by the user. After a match, allow searching from
> > >     location of the match. Provide a case-insensitive search option
> > >     when applicable to the natural language of text. [Priority 2]
> >
> > A further refinement might be to delimit this to visually-displayed text
> > since it is hard to see requiring this (as a minimum requirement) for
> > anything more. Thus (NEW by EH): "7.5 Allow the user to search through text
> > that has been rendered VISUALLY...."
> >
> > New:
> >
> > 7.5 Allow the user to search through text that has been rendered visually.
> > The search must encompass all text within the viewport, both inside and
> > outside the point of regard. Allow the user to start a forward search 
> from a
> > location in content selected or focused by the user. After a match, allow
> > searching from location of the match. Provide a case-insensitive search
> > option when applicable to the natural language of text. [Priority 2]"
> >
> > Comment 1:
> >
> > I focus on visual rendering since we don't expect them to be able to search
> > an audio file.
>
>We don't expect users to search through audio files, only through
>text content (however that text content is rendered, which may be
>as speech). I don't think we need to limit the checkpoint to
>searching through a visual rendering.
>
>  - Ian
>
> > Someone would need to use assistive technology if they needed
> > some kind text-to-speech output.
>
>
>
>--
>Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
>Tel:                         +1 831 457-2842
>Cell:                        +1 917 450-8783

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL  61820

Voice: (217) 244-5870
Fax: (217) 333-0248

E-mail: jongund@uiuc.edu

WWW: http://www.staff.uiuc.edu/~jongund
WWW: http://www.w3.org/wai/ua
Received on Tuesday, 29 August 2000 09:25:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:14 GMT