[nfbcs] JAWS JAWS JAWS

Doug Lee dgl at dlee.org
Mon Feb 4 18:04:26 UTC 2019 

>From the customer standpoint, that would be option 2 in my knowingly oversimplified picture. :-) I say this because that option, and your solution, are the ones that result in delays or outright ignoring of some requests.

To address the original issue:

It sounds like you are saying that things repeat an infinite number of times until you stop speech manually. That is more serious than the average repeating-speech issue. My following remarks are more aimed at things like JAWS
saying a control's name or type two or three times instead of once as you Tab. I am not a regular Outlook user, but if you send exact steps here I can try to repro your issue here in the January JAWS 2019 update. I of course do
not work for FS/Vispero.


Sadly, I have found over the years that many repeating-speech issues are harder than average to track down and fix, because they tend to be caused by separate bits of code that happen unexpectedly to run at or near the same time.

My priorities in speech production, as I script, tend to run like this:

1. Say nothing that is inaccurate or misleading.

2. Say something helpful after a user action.

3. Say only what is necessary or helpful.

4. Say nothing twice.

As you can see, the repeating-speech item drops low in my personal list. My reason, basically, is that it is not misleading, is something, and though it be too much speech, it is easier for users to cut short with Ctrl than,
say, an immensely long group box name, because it both follows and duplicates what important information has already spoken.

On Mon, Feb 04, 2019 at 12:45:31PM -0500, NFBCS mailing list wrote:
Solution:

Prioritize requests against system requirements and customer requests. If
the need outpaces the available staff, as presented, place a higher weight
on those who have proven that they can handle the strain. You must also
increase the wages of the more talented agents there by reducing cost
increases and maximizing production.

End solution.


Charles E. Black, MS.
charleseblack at att.net

-----Original Message-----
From: nfbcs <nfbcs-bounces at nfbnet.org> On Behalf Of Doug Lee via nfbcs
Sent: Monday, February 4, 2019 12:25 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Doug Lee <dgl at dlee.org>
Subject: Re: [nfbcs] JAWS JAWS JAWS

An Economics 101 story problem, where numbers are fictitious since I don't
have real ones:

A company has 50 employees and 50,000 customers. In an average month, 1000
work requests from customers come in.  Each employee has approximately five
hours out of each day in a five-day work week directly for handling customer
work requests. The average time required to fill each of the 1,000 submitted
requests is estimated at ten hours, because of the need to test carefully
after each one to make sure that the changes it produces do not upset
something else that could affect all 50,000 customers.

The company's CEO does the math and figures out that
- One employee needs an average of two days to fill one request.
- If all 50 employees work solidly, this means 25 requests per day will be
filled on average.
- Under ideal conditions, this translates to 40 business days of work to
fill all pending requests from one month.
- In an average month, accounting for holidays, there are about 20 business
days.
- This means that current request-handling capacity is only half of what is
needed to fill all requests.

You are the CEO. Which of the following is your plan for handling this
problem?

1. Hire more employees, thus forcing the price of the product to increase.

2. Filter the work requests down so that only half actually require work.
(Keep in mind, this filtering process itself will also take some of those
employee hours, besides disappointing a lot of customers.)

3. Force employees to fill twice as many requests in the same amount of
time, thus risking quality control problems.

4. A solution that escaped my attention. This is entirely possible; I'm not
a CEO. :-)

Disclaimers:
- I bet the customer count is higher for Vispero. Not sure about employee
count.
- I also think 20 days is a high estimate for number of business days in a
month averaged over a year for the average private-sector company.
- Ten hours per request is an average and is ment to account for a whole
host of things, including occasional major issue resolution requests,
required research, testing on multiple systems, Windows versions, etc.
- Five hours per day for customer requests is probably above reality for
Vispero; after all, even if you ignore meetings and other normal company
hum-drum, innovation and independent research and experimentation are part
of
  the job of a screen reader developer/maintainer.

On Mon, Feb 04, 2019 at 11:42:41AM -0500, NFBCS mailing list wrote:
Don't you hate when a company refuses to patch certain bugs?


On 2/4/2019 6:39 AM, Vincent Martin via nfbcs wrote:
> I have the same problem as well.
> 
> -----Original Message-----
> From: nfbcs <nfbcs-bounces at nfbnet.org> On Behalf Of David Andrews via 
> nfbcs
> Sent: Monday, February 4, 2019 12:51 AM
> To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> Cc: David Andrews <dandrews at visi.com>
> Subject: Re: [nfbcs] JAWS JAWS JAWS
> 
> I have had that problem for the last couple builds.  I reported it to 
> JAWS at least six months ago, and they said they couldn't reproduce 
> it.  I have it on three different machines.
> 
> Dave
> 
> At 11:30 PM 2/3/2019, you wrote:
> > Is anyone else having the problem with the latest update of JAWS 
> > that it keeps repeating itself unless you press control? It happens 
> > the most for me in the message list of Outlook.
> > 
> > 
> > 
> > Nicole
> 
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/vincentfmartin2020%
> 40gmai
> l.com
> 
> 
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%40g
> mail.com

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


_______________________________________________
nfbcs mailing list
nfbcs at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for nfbcs:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/dgl%40dlee.org

-- 
Doug Lee                 dgl at dlee.org                http://www.dlee.org
Level Access             doug.lee at LevelAccess.com
http://www.LevelAccess.com
"The nice thing about standards is that there are so many of them to choose
from." -- Andrew Tanenbaum

_______________________________________________
nfbcs mailing list
nfbcs at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for nfbcs:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/charleseblack%40att.net


_______________________________________________
nfbcs mailing list
nfbcs at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for nfbcs:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/dgl%40dlee.org

-- 
Doug Lee                 dgl at dlee.org                http://www.dlee.org
Level Access             doug.lee at LevelAccess.com    http://www.LevelAccess.com
"Pray devoutly, but hammer stoutly."
--Sir William G. Benham

More information about the NFBCS mailing list