[jawsscripts] Re: Accessibility, Usability and Scripting

From: "Don Mauck" <don.mauck@xxxxxxxxxx>
To: "jawsscripts@xxxxxxxxxxxxx" <jawsscripts@xxxxxxxxxxxxx>
Date: Thu, 4 Oct 2007 11:58:28 -0600
I'm in a position to check that out so I will. 



Oracle
Don Mauck | XAU Developer
Cross Applications Unlimited
7700 Technology Way
Denver CO 80237
Phone (303) 334-4184
Email don.mauck@xxxxxxxxxx 

-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx 
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of John Robichaud
Sent: Thursday, October 04, 2007 11:16 AM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Accessibility, Usability and Scripting

The concept of accessibility is only meaningful within the context that the 
application is actually used. For example, a database screen that displays 40 
fields of data may be considered accessible for an upper level manager who can 
take the time to tab to whatever field of data he/she needs to read.
This same screen can be considered inaccessible, however, to the customer 
service rep who must access that same data field immediately while interacting 
with a customer on the telephone. The service rep cannot realistically depend 
on tabbing to obtain such data. The only way to read such data efficiently is 
via scripting.
Oracle's Forms (Oracle's version of Java) is notoriously deficient in this 
regard because they cannot be scripted. This is a common problem in employment 
situations.
John Robichaud


-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx]On Behalf Of Don Mauck
Sent: Thursday, October 04, 2007 12:20 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Accessibility, Usability and Scripting


From an Oracle standpoint, we are continually working with all Oracle 
Applications to insure that little if any scripting take place to insure 508 
compliancy.  It does none of our clients any good if they need to spend 
additional time and money to install special scripts to make our products work. 
 In that vein, we will be spending a lot of effort in revamping the Siebel 
products for example to insure that the meet 508 as well as the European 
standards for accessibility compliancy. I don't believe that a user of a 
product should be forced to learn a scripting language or pay some one to do it 
for them to make the product work.



Oracle
Don Mauck | XAU Developer
Cross Applications Unlimited
7700 Technology Way
Denver CO 80237
Phone (303) 334-4184
Email don.mauck@xxxxxxxxxx

-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Geoff Chapman
Sent: Wednesday, October 03, 2007 8:24 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Accessibility, Usability and Scripting

yeah all agreed in theory daniel,
but unfortunately in the practical real world daniel, you just don't always get 
work place systems, or consumer software developers for that matter, to wanna 
bother, or even no how if they wanna bother, to make their systems accessible 
from the back end!

----- Original Message -----
From: "Daniel Tang (dtang)" <dtang@xxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Thursday, October 04, 2007 3:10 AM
Subject: [jawsscripts] Re: Accessibility, Usability and Scripting


Hello all:

If an application requires scripting work before it is usable by people with 
disability, *that application is not accessible. Scripting only remedies the 
problem. If the application is conceived to be used by all, it should be used 
by regular jaws keystrokes and hot keys. Scripting takes extra time and cost 
before it is usable. Yes. Scripting can be helpful by making it accessible 
temporarily. But when the application releases subsequent versions, scripting 
must be done again. Therefore, the users again are behind; need to wait a 
scripter to do the job before they can use it.



Daniel Tang
Email: dtang@xxxxxxxxx

-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of David W Bundy
Sent: Tuesday, October 02, 2007 6:03 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Accessibility, Usability and Scripting

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
__________
View the list's information and change your settings at 
http://www.freelists.org/list/jawsscripts
__________
View the list's information and change your settings at 
http://www.freelists.org/list/jawsscripts


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

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


__________ 
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
References:
- [jawsscripts] Re: Accessibility, Usability and Scripting
  - From: John Robichaud
[jawsscripts] Re: Accessibility, Usability and Scripting

Other related posts:
