W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 1999

Re: A couple of comments

From: Scott Luebking <phoenixl@netcom.com>
Date: Wed, 1 Dec 1999 09:20:17 -0800 (PST)
Message-Id: <199912011720.JAA11290@netcom.com>
To: ij@w3.org, phoenixl@netcom.com
Cc: w3c-wai-ua@w3.org
Hi, Ian

I was thinking that the section called "User interface issues"
was discussing issues to keep in mind in terms of user interfaces.
A challenge in the user interface world is handling dynamic
presentation of information based on the semantic content rather than
the syntactic structure.  Computers can do syntactic transformation
rather easily since they need not understand the semantic meaning
of the information.  However, what blind users will benefit more from
will be interfaces which can also understand the semantic nature
of the information and make appropriate choices on that basis.
How it will be done is a challenge.

Scott


> Scott Luebking wrote:
> > 
> > Hi,
> > 
> > Just a few comments.
> 
> Hi Scott,
> 
> Most of your comments are very good ideas for the Techniques
> document and I will integrate them there (and I've snipped
> them out of my comments below). 
>  
> > Check points:
> > 
> > 4.10 Allow the user to start, stop, pause, and rewind video.
> > 4.13 Allow the user to start, stop, pause, and rewind audio.
> > 
> >     These two checkpoints should have incremental forward and back up.
> >     Media players of different types often have a slide bar which
> >     can be hard for blind users or mobility impaired people to use.
> >     Buttons for incremental back up and forward are easier to use.
> >     The incremental back up is especially useful for those situations
> >     where the sound is momentarily not understandable, e.g.  truck
> >     passing by, announcement over a speaker phone.
> 
> Added as issue 135
> http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#135
> 
> > 4.14 Allow the user to control synthesized speech playback rate.
> > 
> >     Incremental back up might be useful here also.
> 
> Also added in issue 135
>  
> > Techniques:
> > 
> > 2.1
> > 
> >     User interface issues
> > 
> >     Another user interface issue is making intelligent decisions
> >     concerning rendering and layout based not only on structure
> >     of content, but also on the subject matter / information in the
> >     content.
> 
> How is this done?
> > 
> > GENERAL COMMENTS
> > 
> > I think there should be a strong statement at the beginning of document
> > about the need to have disabled people in the process of designing
> > and testing the software.  It probably should say that the guidelines can
> > help avoid pitfalls, but it is quite possible to follow the guidelines
> > and still end up with an inaccessible user agent.
> 
> That's a good idea, although I'm not sure where in the beginning
> of the document this would go. 
> 
> We have a section entitled "Testing UA operation with platform
> standards" in the Techniques document and this should be emphasized
> there.
>  
> Thanks again Scott,
> 
>  - Ian
Received on Wednesday, 1 December 1999 12:21:21 GMT

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