I am writing this response with NVDA. It's working fine. It's definitely a
JAWS issue, although it exists with two different versions of JAWS, so I
don't think it is a setting I accidentally changed.
Dennis from VFO said he has not gotten a bunch of complaints, so he thinks
it's an Office issue.
Very strange.
From: vibug-support-bounce@xxxxxxxxxxxxx
[mailto:vibug-support-bounce@xxxxxxxxxxxxx] On Behalf Of David Kingsbury
Sent: Wednesday, March 22, 2017 6:37 PM
To: vibug-support@xxxxxxxxxxxxx
Subject: [vibug-support] Re: Office 365 Problem
Perhaps try preparing a message using NVDA, just to see if you can isolate
this as a JAWS problem.
From: vibug-support-bounce@xxxxxxxxxxxxx
<mailto:vibug-support-bounce@xxxxxxxxxxxxx>
[mailto:vibug-support-bounce@xxxxxxxxxxxxx] On Behalf Of Jerry Berrier
Sent: Wednesday, March 22, 2017 6:07 PM
To: vibug-support@xxxxxxxxxxxxx <mailto:vibug-support@xxxxxxxxxxxxx>
Subject: [vibug-support] Office 365 Problem
I am running JFW 18 on a relatively new Lenovo laptop running Windows 10.
This problem also occurs with JAWS 17 also.
I took my laptop with me yesterday on a trip to DC. Somehow I am no longer
able to compose e-mails in Outlook. I can read them, and I can even read
and edit a draft I created on my other computer, but I cannot compose or
reply to e-mails. Everything is fine until I get to the body of the
message. Then somehow quick nav seems to get turned on and I cannot turn it
off. If I hit insert-z it says unavailable.
H says no more headings, etc.
As soon as I tab from the subject to the body, JAWS says message not
available.
The VFO guys said I need to make sure I'm running the latest version of
Office 365; I checked and I am.
I have checked my message settings and view settings, and I can find nothing
there.
I got a sighted person to compose an e-mail without JAWS running, and she
said it worked fine and looked perfectly normal.
Any thoughts?
