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

Re: Refinements and additions to minimum set of functions forsingle command checkpoint (bookmarks/favorites )

From: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
Date: Tue, 25 Jul 2000 10:47:03 -0500
Message-Id: <4.3.1.2.20000725104505.012e2788@staff.uiuc.edu>
To: Ian Jacobs <ij@w3.org>
Cc: Al Gilman <asgilman@iamdigex.net>, Jon Gunderson <jongund@uiuc.edu>, w3c-wai-ua@w3.org
Ian,
I was under the assumption that we using the applicability clause, just 
like with other checkpoints.  If you have this function provide single key 
access.  Did anyone have another understanding?

3) Indicate clearly that some of the bindings only apply if
    the feature has been implemented (e.g., history mechanism,
    favorites, mechanism, etc.). Also indicate that some of
    the bindings are for functionalities that are required by
    the UA Guidelines (e.g., navigation to active elements).

Jon


At 09:20 AM 7/25/2000 -0400, Ian Jacobs wrote:
>Jon Gunderson wrote:
> >
> > >
> > >I just want to note that we have no requirement on the
> > >user agent to implement a bookmarks feature. Having a P1 requirement
> > >to provide single command access to such a feature is problematic
> > >for me. Unless we add a P1 requirement to implement such a feature.
> > >Most of the other bindings in the proposed list have corresponding
> > >checkpoints (e.g., navigation of active elements).
> > >
> > >So, I think we need to make the requirement explicit
> > >in order to determine the appropriate priority level. I don't think
> > >that single command access to a P2 required functionality should
> > >be P1.
> > >
> > >  - Ian
> >
> > JRG: Checkpoint 10.5 is currently a P2 requirement.  I don't understand
> > what functionality you are referring to as a P1 requirement.  Could you
> > explain?
>
>The list of functionalities one must be able to activate with
>a single command includes adding a page to one's favorites. But
>the UA Guideilnes does not require that the UA implement
>a favorites mechanism. If we require a binding to a function
>then that implies that we also are requiring the function.
>Unless the applicability clause is invoked. And that has not
>been made clear.
>
>Therefore, choose one of the following:
>1) Add a requirement to have a favorites functionality.
>2) Remove the functionalities related to favorites from the
>    list of required bindings.
>3) Indicate clearly that some of the bindings only apply if
>    the feature has been implemented (e.g., history mechanism,
>    favorites, mechanism, etc.). Also indicate that some of
>    the bindings are for functionalities that are required by
>    the UA Guidelines (e.g., navigation to active elements).
>
>  - Ian
>
>
>--
>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, 25 July 2000 11:46:16 GMT

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