W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 1998

RE: some comments.

From: David Poehlman <poehlman@clark.net>
Date: Fri, 22 May 1998 15:47:20 -0400 (EDT)
To: "Charles (Chuck) Oppermann" <chuckop@MICROSOFT.com>
cc: "'Jon Gunderson'" <jongund@staff.uiuc.edu>, w3c-wai-ua@w3.org
Message-ID: <Pine.GSO.3.96.980522154527.17953C-100000@shell.clark.net>
msaa is implimented but not the current release in screenreaders that I
know of.  Nor will it be any time soon before the projected version of
msaa is impliimented by screenreaders.  Also, the success of msaa depends
on the mainstream side to use it as well.  as far as I know, there are two
products that currently utilize msaa word and msie.


On Tue, 19 May 1998, Charles (Chuck) Oppermann wrote:

> <<
> ---priority 2: lots of 3rd party access is going to be slow to impliment
> msaa 
> >>
> Actually, all major screen readers implement Active Accessibility as a
> client.  In addition, several alternative input packages, such as On-screen
> keyboards and voice-input packages use Active Accessibility.  The acceptance
> of MSAA in just one year has been phenomenal.
> 
> Charles Oppermann
> Program Manager, Active Accessibility, Microsoft Corporation
> mailto:chuckop@microsoft.com http://microsoft.com/enable/
> "A computer on every desk and in every home, usable by everyone!"
> 
> -----Original Message-----
> From: Jon Gunderson [mailto:jongund@staff.uiuc.edu]
> Sent: Tuesday, May 19, 1998 1:59 PM
> To: David Poehlman; w3c-wai-ua@w3.org
> Subject: Re: some comments.
> 
> 
> David,
> On today's conference call there was concern for naming specific
> accessibility API like Active Accessibility or SunSoft Java Accessibility
> API.  There was a suggestion to be more generic in stating that system
> accessibilitiy APIs should be used and lists these as potential sources.
> Jon
> 
> 
> At 10:38 AM 5/19/98 -0400, David Poehlman wrote:
> >Usage of ALT and TITLE:
> >       ALT: Image description.--- might be better as: "text replacing
> image".
> >       TITLE: Tool tip
> >
> >  D. Alternative Representations for Video, Movies and Annimations
> >  
> >    1. [Priority 1]
> >       User selectable option is available to turn on audio descriptions
> >       of videoes, movies and annimations for videos.
> >    2. [Priority 1]
> >       User selectable option is available to turn on closed captioning
> >       of video, images and annimations.
> >---I'd like to be able to turn them on or off.
> >
> >    3. [Priority 2]
> >       Extended document summary information is displayed on user
> >       command.
> >---we might consider changing this to priority one.
> >
> >---as part of a brief summary appearing on the status line we might
> >consider it dynamic partly and include a percentage of page pointer
> >in text somehow.  this can be gotten from the scroll bar.
> >
> >---I'd add a priority 1 to accessability menus to render all toolbars
> >in text. that may not be the place to put it but it is an alternative
> >menu view.
> >   
> >5. Compatibility with 3rd Party Assistive Technology
> >
> >  A. Standard OS Controls/Menus/Dialog boxes
> >--- priority 1.  
> >   Using standard rather than custom controls in the designing browser
> >   applications increases the accessibility of the application. Third
> >   party assistive technology developers are more likely able to access
> >   standard controls than custom controls. If you must use custom
> >   controls review them for accessibility or check for controls that
> >   support Active Accessibility or the SUN Soft Accessibility API (see
> >   following sections).
> >   
> >  B. Microsoft Active Accessibility in Windows 95/NT versions.
> >  ---priority 2: lots of 3rd party access is going to be slow to impliment
> msaa 
> >   When developing new applications for Windows 95/NT build into the
> >   specifications and design active accessibility compatibility. This
> >   provides 3rd party asssistive technology with important information
> >   for accessibility about your program for persons using 3rd part
> >   assistive technology. More information on active accessibility can be
> >   found at [43]Microsoft WWW site on Active Accessibility.
> >   
> >  C. SUNSoft Java Accessibility API in Java Code
> >  
> >   When developing new applications using SUNSoft Java technology build
> >   into the specifications and design the use of the Java Accessibility
> >   API. This provides 3rd party asssistive technology with important
> >   information for accessibility, so persons with disabilities can use
> >   assistive technology to more efficiently access your programs. More
> >   information on Java Accessibility API can be found at [44]Java
> >   Accessibility Utilities.
> >     _________________________________________________________________
> >
> >
> >Hands-On-Technolog(eye)s
> >touching the internet
> >voice: 1-(301) 949-7599
> >poehlman@clark.net
> >ftp://ftp.clark.net/pub/poehlman
> >http://www.clark.net/pub/poehlman
> >
> >
> 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
> 

Hands-On-Technolog(eye)s
touching the internet
voice: 1-(301) 949-7599
poehlman@clark.net
ftp://ftp.clark.net/pub/poehlman
http://www.clark.net/pub/poehlman
Received on Friday, 22 May 1998 15:47:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:20 UTC