E-mail List Archives

Search E-mail List Archives for

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

From: priti
Date: Mon, Aug 21 2006 11:20PM
Subject: Re: I created a Log-In that doesnt appear tobeaccessibletoJaws
No previous message | No next message

Hi John,

I would like to know the standard conventions, which are mentioned in the
reply you got. I am using JAWS from the past 5 years, and have never come
across any conventions asking the user to turn forms mode 'On' in an edit
field of a dialog box.

JAWS informs us that it is a dialog box, and to my knowledge a user does not
require to turn forms mode 'On' to type in the edit field of a dialog box.
As far as I am concerned, the log in screen is perfectly accessible. Also I
would like to learn more about the standard conventions if any thing I am
not aware off and if the same are known to you.

Regards,
Priti.rohra
Accessibility Tester
Net Systems Informatics (I) Pvt. Ltd.
India
Tel: 91-22-26860485/6 extn: 28
E-mail: = EMAIL ADDRESS REMOVED =
Url: www.n-syst.com


----- Original Message -----
From: < = EMAIL ADDRESS REMOVED = >
To: "'WebAIM Discussion List'" < = EMAIL ADDRESS REMOVED = >
Sent: Monday, August 21, 2006 11:13 PM
Subject: RE: [WebAIM] I created a Log-In that doesnt appear to
beaccessibletoJaws


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 __________________