Re: Some comments to current draft

Response with JRG:

At 12:56 PM 6/3/1998 +0300, Marja-Riitta Koivunen wrote:
>WAI Guidelines: Browser User Interface
>
>Here are my comments. I tried to leave out the ones that were already
discussed yesterday but there might still be some. Sorry about this.
>
>1 Rating and Classification
>
>The link behind "one or more users" is good. However shouldn't we include
also TABs (temporary di-sappled) to this list and explain how these
features benefit also people in noisy environments, environ-ments were
noise is not tolerated (library, cubicles area, when children are asleep
etc.), people with wi-reless devices, people whose hands are tied or
concentration is low (e.g. driving a car) etc. etc. This would emphasize
the benefits to almost everyone in some environment.

JRG: good point.  I will send this item to the Page Authoring group
developing the central document.

>
>2.3  Selection ...
>
>Activation is the user commanding the browser ... 
>Maybe this is perfect english but I think it can be said more clearly.
(Activation means that... or Activa-tion is the action when user ...)
>
>3.1  Control over Browser ...
>
>This was discussed already. I just would like to clarify my suggestion of
allowing the users create cus-tomized switch sets (e.g. a window with check
boxes where fonts, images, colors, tables etc. are selec-ted or turned
on/off/leave as is) these sets can then be named and presented as buttons
or menu items. When a button is selected it activates the switches and
selections unless they are "leave as is". Some readymade definitions could
be available for instance only text or only sound button. This would allow
users a way to easily change the attributes they wish in bundles that suit
them.

JRG: I will add a section under visibility for a configuration section of
the browser for persons with disabilities.

>
>3.3  Alternative Repres...
>
>1.  Allow the user to turn on audio descriptions of videos, movies, and
animations.
>I think that audio descriptions can be also defined within HTML OBJECT,
shouln't we be able to turn these on and off also and display the
alternative text or longdesc instead? I guess the type of an OB-JECT tells
if it is an image or something else.
>

JRG: This primarily relates to synchronous descriptions as images change on
the screen and is described through an audio file.  This can be done using
the SMIL specification. 

>3. Provide a serialized view of tables
>This could be more flexible. At least the user should be able to toggle
between rows first/columns first serialization. The summary of the table
should probably be a switch too that can be turned off and on.

JRG: These requests seem to be dependent on the table purpose.  The user
will probably not know what they want until they read the table.  This will
require the browser to reload the table with a different format.   

>
>4.1 Maintenance of Document View and Focus
>
>As a user activates links and returns to previously visited documents that
their last view and focus in the document remain the same. 
>--- change to: As user returns to a previously visited document the last
view and focus in the document should remain the same.
>For how long? Until next activation of the browser?

JRG:  I don't think we need to specify this.  But, we could say for the
duration the browser is running.

>
>5.1 Sequential navigation
>Why not also between OBJECTs. I don't think it matters to the user if the
designer used IMG or OB-JECT tag to define a picture.

JRG: There will only be a TAB stop if the image is a link.

>
>5.2 Hierarchical Navigation
>Is hierachy a separate window?

JRG:  It could be a separte window.  Or could be an alternative view of the
document.  Is there a reason to be more specific in the implementation?

>
>5.6 Dynamic HTML elements
>
>2.  Is this a specific view or window?
>
>6.1 Menu Commands
>2.  Maybe the menus and iconbars should be customizable allowing these
commands rather than forcing everybody to use them?

JRG: The primary reason to display short cuts is to make them more visible
to able bodied persons, so if they help somebody with a disability they may
be aware of the keyboard short cuts.

>
>7.2 Compatibility ...

>Last word in chapter is There
>
>
>
Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
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
	http://www.als.uiuc.edu/InfoTechAccess

Received on Thursday, 4 June 1998 12:11:29 UTC