[jawsscripts] Re: Accessibility, Usability and Scripting

  • From: "David W Bundy" <sharktrainer13@xxxxxxxxx>
  • To: <jawsscripts@xxxxxxxxxxxxx>
  • Date: Tue, 2 Oct 2007 21:02:45 -0400

If a blind employee is not able to access the program with JAWS in such a way 
that they can be competative with their sighted co-workers, then the program is 
not accessible from my perspective.  When I script an application, I want to go 
beyond just being able to get to the information, but to be able to get to it 
in as timely a manner as possible, so I add in shortcuts go gather the most 
frequently used information or get to the most frequently used fields.  
Typically, job performance is measured by how quickly a given task is 
accomplished, so anything we can do to give our consumers a competative edge 
should be done as a matter of course.

David
 

-----Original Message-----
.From: "Geoff Chapman"<gch@xxxxxxxxxxxxxxxx>
.Sent: 10/1/07 10:55:08 PM
.To: "jawsscripts@xxxxxxxxxxxxx"<jawsscripts@xxxxxxxxxxxxx>
.Subject: [jawsscripts] Re: Accessibility, Usability and Scripting
.
.my input is, I heartily agree with you! 
.  ----- Original Message ----- 
.  From: Kamil 
.  To: jawsscripts@xxxxxxxxxxxxx 
.  Sent: Tuesday, October 02, 2007 12:27 PM
.  Subject: [jawsscripts] Accessibility, Usability and Scripting
.
.
.  Hi folks,
.
.  I would like to know your take on a subject which raises hot debats in my 
workplace and that is how much scripting is really necessary for an application.
.
.  Based on this business standards, application accessibility means the 
existance of methods for getting the information on the screen and interact 
with it. 
.
.  It doesn't take into account, the time it takes to reach to a specific piece 
of information and the needed energy to filter the unwanted announcements.
.
.  The JAWS cursor is not only, not assumed the last resort, but also is 
assumed to be used, as the main tool for static information retrieval, 
according to this standard.
.
.  This way, other than applications with graphic components without 
alternative text, the rest can be catagorized accessible since by using JAWS 
cursor eventually one can get to any place and if direct keyboard interaction 
is not possible then keyboard equivalents of mouse clicks can be utilized.
.
.  The rest falls in the realm of usability.
.
.  The business believes that it's responsible to provide accessibility as 
defined above and anything beyond that is just icing on the cake.
.
.  My approach to this subject, is to see the big picture. Taking into account 
all the stress, frustration and the time that is getting wasted navigating a 
not properly laid out screen together with filtering unwanted audio data.
.
.  This way not only total accessibilty should be provided but a highly usable 
interface is the winning card.
.
.  What I mean by highly usable interface, is a kind of intelligent interface 
for the application which provides such facilities as:
.  Instant anouncement of the value of each field by typing the very first 
letters of its label
.  Automatic announcement of live data when they change
.  Availability of hotkeys to activate major tasks 
.  Suppressing extra announcements
.
.  I highly appreciate your input.
.
.  Thanks,
.
.  Kamil
.
.
.   

__________ 
View the list's information and change your settings at 
http://www.freelists.org/list/jawsscripts

Other related posts:

  1. Home
  2. jawsscripts
  3. Archive
  4. 10-2007