Subject line has my question really, but I've noticed, presumably along with
many of you, that sometimes, Jaws justt seems to capture/autospeak relevant
information on a page when it changes/appears, and other times, it sure
doesn't. this thread prompted me to wanna ask if anyone out here might know
just why that is? I.e. what we might be able to tell site developers to improve
sites, where this doesn't occur? And the blind user is left stumbling around
the site lots to find out what's happening in response to an action they've
just performed?
I've run across this in lots of situations, but I guess most communicably, in
scenarios where one has filled in a form, and hit "submit," and there's been
some error in the form, and the site then attempts to alert the user to the
field that's problematic.
Some sites do a fantastic job of this, not only causing JAWS to autospeak the
error message/problem, but once in a while, (not often mind you), I think I've
even seen focus moved automatically to the problematic field! More often than
not of course though, the user simply assumes there's an error, because they
haven't heard any new page load information, and then has to maybe do a JAWS
find for the word "error", to look for the message manually themselves. Or
arrow down line by line till they find something informative.
And then, the error might simply say that the problematic field is "marked in
red colour", which is obviously not that helpful either, although I realise we
can move through each field, and keep hitting JawsKey+TopRow number 5, to check
the foreground and background colour etc.
I realise this is a tad off topic for a jaws Scripting list, but, ... well the
knowledge up here seems quite astounding, and, the answer would probably help a
lot of us, if there was one that anyone happened to know?
Or, to bring it more back on topic, if there's any scripting functionality that
we can introduce, that may help "catch"/automatically speak, new important
information that the site throws on to the page, that the user needs to know?
Any thoughts/discussion most welcome anyways.
Regards
Geoff C.
----- Original Message -----
From: John Robichaud <John_Robichaud@xxxxxxxxxxx>
Reply-To: <jawsscripts@xxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: 7/04/2020 2:39:48 AM
Subject: [jawsscripts] Re: what function causes a page opening in Chrome to
speak automatically
________________________________________________________________________________
Thank you Csaba. I've been away from it for a while but this will help.
John
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Csaba Árpádházy-Godo
Sent: Thursday, February 20, 2020 2:14 AM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: what function causes a page opening in Chrome to
speak automatically
HiJohn,
In JCF the following entry can control this behaviour:
[HTML]
SayAllOnDocumentLoad=1
In code, you have to look in default.jss for the following events &
functions:
DocumentLoadedEvent
DoDefaultDocumentLoadActions
ShouldSayAllOnDocumentLoad
The last one is responsible to say all if the above mentioned setting is set to
true.
HTH
Czaba
2020. 02. 19. 21:42 keltezéssel, John Robichaud írta:
I'm trying to determine which Jaws function causes a page opening in__________
Chrome to speak automatically. I'd like to alter that behavior. Can
anyone help here?
John Robichaud
__________
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts