E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 1 (In chronological order)

From: jmoyn2339
Date: Mon, Aug 21 2006 11:50AM
Subject: RE: I created a Log-In that doesnt appear to beaccessibletoJaws
No previous message | No next message

Hi Priti,
I received a reply from another person indicating the following. I was
wondering what your feelings were. I'm not certain if I need to change
anything with this log in.

Thanks,
John
___________________REPY THAT I RECEIVED__________________
Hi John,



Actually, the log in screen is completely accessible, it is just that it
doesn't follow the standard conventions that speech users expect, i.e.:



Generally, when a speech (JAWS or Window-

Eyes) user gets to an edit field, multi-select list box or combo box, she
will need to hit "ENTER" in order to engage active text-editing capabilities
(called "forms mode" by JAWS and "MSAA mode" by Window-Eyes). It is not
until the user hits "ENTER", that a blinking cursor appears in the edit
field (much in the same way sighted users must click the mouse on the edit
field). After finishing the text entry, the speech user hits "ENTER" again,
to exit "forms/MSAA mode" and submit the form.



The fields in your log in screen are unusual in that they do not require the
user to hit "ENTER" in order to type in text. Thus, they will probably be
confusing to most speech users. Speech users who are familiar with standard
conventions will keep hitting "ENTER", expecting to activate the edit
cursor, but, instead they will just keep submitting a blank form, every time
they hit "ENTER" on your log in screen.



I hope this makes sense. My only suggestion for correcting the "problem" is
to adhere to standard conventions that require users to "click" in the form
in order to engage an edit cursor. Please feel free to phone or email me
if you need additional clarification.


___________________ END OF REPLY __________________