[jawsscripts] Re: Accessibility, Usability and Scripting

  • From: "inthaneelf" <inthaneelf@xxxxxxxxxxxxxx>
  • To: <jawsscripts@xxxxxxxxxxxxx>
  • Date: Mon, 1 Oct 2007 23:26:19 -0700

I must apologize for the way my first post sounded, I agree with you Kamil , 
and the "wrong answer" statement goes to the other folks, nonononono! there 
definition is not "accessibility" not by a long shot!

tell them if they will use your standard, that they can double or triple 
output, not only by the visually impaired, but it can speed up access for the 
non visually impaired due to lack of clutter and faster access to the needed 
information.  

regards, 
inthane
. For Blind Programming assistance, Information, Useful Programs, and Links to 
Jamal Mazrui's Text tutorial packages and Applications, visit me at:
http://grabbag.alacorncomputer.com
. to be able to view a simple programming project in several programming 
languages, visit the Fruit basket demo site at:
http://fruitbasketdemo.alacorncomputer.com

  ----- Original Message ----- 
  From: Geoff Chapman 
  To: jawsscripts@xxxxxxxxxxxxx 
  Sent: Monday, October 01, 2007 7:55 PM
  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

Other related posts:

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