[blindLaw] SOS --Need for Testing Beta 2020 and Microsoft 2016

Fri Oct 11 20:22:09 UTC 2019

Yes, the requirement to use specific versions of Office, etc. is I think quite common. I’ve experienced this at both of my firms.

Angie

Angela Matney, CIPP/US
Attorney at Law
[Loeb & Loeb LLP]<http://www.loeb.com/>
Loeb and Loeb LLP
901 New York Avenue NW, Suite 300 East | Washington, DC 20001
Direct Dial: 202.618.5038 | Fax:202.403.3407 | E-mail:amatney at loeb.com<mailto:amatney at loeb.com>
Los Angeles | New York | Chicago | Nashville | Washington, DC | San Francisco | Beijing | Hong Kong | www.loeb.com<http://www.loeb.com/>

________________________________
CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender. Please destroy the original transmission and its attachments without reading or saving in any manner. Thank you, Loeb & Loeb LLP.
________________________________
From: BlindLaw <blindlaw-bounces at nfbnet.org> On Behalf Of Laura Wolk via BlindLaw
Sent: Friday, October 11, 2019 4:16 PM
To: Helga Schreiber <helga.schreiber26 at gmail.com>
Cc: Laura Wolk <laura.wolk at gmail.com>; Blind Law Mailing List <blindlaw at nfbnet.org>
Subject: Re: [blindLaw] SOS --Need for Testing Beta 2020 and Microsoft 2016

Hi James,

Yes I'm on 2016, and I do need it to be tested with 2016
unfortunately. I can't go into details, but for good reason, I can't
switch to 365 or NVDA. Which is why Microsoft and Vispero's attitudes
are so ridiculous. Because I'm far from the only one in this
situation. For a variety of security or compatibility reasons, many
companies won't let one person use 365 while everyone else is on 2016.
I really do appreciate your concern. I hope I am able to keep a level
head when speaking to them all.

Laura

On 10/11/19, Helga Schreiber <helga.schreiber26 at gmail.com> wrote:
> Hi all again. In my last email message, I ment to ask if you guys have try
> to deal with tracck changes using pages or office 2016 with Voiceover on the
> Mac computer? If not, I was thinking that could help some of you to try to
> test it out if yu have the Mac. Thanks again.
>
> Helga Schreiber
> Email Address: helga.schreiber26 at gmail.com
> Sent from my iPhone 8
>
>
>
>> On Oct 11, 2019, at 3:38 PM, Helga Schreiber <helga.schreiber26 at gmail.com>
>> wrote:
>>
>> Hi Laura and all. Well, I’m not a law school student yet, but I’m in the
>> process of getting there. Due to that, I have not deal yet with track
>> changes with word document. However, I have a suggestion if some of you
>> could try if you have a Mac computer. Have you try to complete the track
>> changes in Micrsoft word document using Voiceover in the Mac? I’m assuming
>> this could work with pages and offfice 2016 that is I heard is accessible
>> with Voiceover on the Mac. Hopefully these suggestions help some of you.
>> Look forwrd to hear form you soon. Thanks so much.
>>
>> Helga Schreiber
>> Email Address: helga.schreiber26 at gmail.com
>> Sent from my iPhone 8
>>
>>
>>
>>>> On Oct 11, 2019, at 2:46 PM, Laura Wolk via BlindLaw
>>>> <blindlaw at nfbnet.org> wrote:
>>>>
>>> All,
>>>
>>> The nightmarish scenario of Jaws reading all material,both old and
>>> new, in a track changed document seems to have arisen with a vengeance
>>> as of the late September release. I have tried restarting jaws,
>>> restarting the computer, refreshing the screen, and switching to no
>>> markup. Nothing works.
>>>
>>> My ability to work quickly and reliably has just been ground to a
>>> screeching halt. Why not simply migrate back to an earlier update,
>>> you might ask? Well, my friends, it's because **that** update was
>>> causing heavily track changed documents to crash as soon as the
>>> document was opened. And how did Vispero come to know that fact?
>>> Because they tested it and identified hhe problem and committed
>>> themselves to fixing it as soon as possible? No, of course not.
>>> Because my coworkers and I spent hours, literally hours, isolating the
>>> problem, creating a test document with nonsensitive information that
>>> replicated it, and sending it to them. I am truly at my whits end. I
>>> am a fully-employed person with a disability working at one of the
>>> most stressful and time consuming jobs in our profession. And yet,
>>> here I am, using my work time to literally sit on the phone and
>>> **explain**, yes, **EXPLAIN, step-by-step, to Vispero employees how to
>>> **TURN ON Track CHANGES**, because they are so unfamiliar with this
>>> concept that they don't even know how to do it. I do not have the
>>> time to take on a second full-time job just so I can do my first one.
>>> None of us do. This is utterly unacceptable. We need our leadership
>>> to step in now. Stop bringing Microsoft to national conventions to
>>> wax eloquent about how much they care about accessibility if in fact
>>> they don't. If in fact they are committed to not assisting at all
>>> with products that people still pay them to suppor, products that the
>>> entire federal government uses, products that just ask the blind to
>>> deal with it or risk losing their jobs. Stop touting Jaws as if it's
>>> the best thing since sliced bread if, one week into the Supreme Court
>>> term, I now effectively cannot do my job, no, not have a harder time
>>> doing my job, but cannot do my job, because no one is testing this
>>> stuff before updates are released. I am just incensed.
>>>
>>> I also need someone to test whether this problem is occurring on Beta
>>> 2020 with Word 2016. I cannot get beta 2020 installed on my computer
>>> here. But I need to verify whether it's fixed in that release. I
>>> swear, if they try making me wait until December to fix this, I'm
>>> going to need some major reinforcements.
>>>
>>> Now please excuse me while I quickly go angry cry in the bathroom, put
>>> on my nice happy brave face again, and resign myself to spending
>>> thrice as much time on my work as I needed to spend yesterday. Your
>>> prayers are appreciated.
>>>
>>> _______________________________________________
>>> BlindLaw mailing list
>>> BlindLaw at nfbnet.org
>>> http://nfbnet.org/mailman/listinfo/blindlaw_nfbnet.org
>>><http://nfbnet.org/mailman/listinfo/blindlaw_nfbnet.org%3cBR%3e%3e%3e%3e> To unsubscribe, change your list options or get your account info for
>>> BlindLaw:
>>> http://nfbnet.org/mailman/options/blindlaw_nfbnet.org/helga.schreiber26%40gmail.com
>

_______________________________________________
BlindLaw<http://nfbnet.org/mailman/options/blindlaw_nfbnet.org/helga.schreiber26%40gmail.com%3cBR%3e%3e%3cBR%3e%3cBR%3e_______________________________________________%3cBR%3eBlindLaw> mailing list
BlindLaw at nfbnet.org
http://nfbnet.org/mailman/listinfo/blindlaw_nfbnet.org
To unsubscribe, change your list options or get your account info for BlindLaw:
http://nfbnet.org/mailman/options/blindlaw_nfbnet.org/amatney%40loeb.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2157 bytes
Desc: image001.jpg
URL: <http://nfbnet.org/pipermail/blindlaw_nfbnet.org/attachments/20191011/f777eb3b/attachment.jpg>