Hello Jonnathan. How do I get the build for Office 365?
Thanks so much.
Paul
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Jonathan Cohn
Sent: Thursday, December 28, 2017 4:06 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Making part of an application Accessible
Again, which OS and which version of Office. If Windows 10 and/or Office
365 then , please include the build number.
Microsoft is making significant changes in the accessibility of all their
products. But in general JAWS often uses VBA scripting to get the
information it needs. So if you want to make something accessible that is
not in Office you probably need to figure out how to access that information
in visual basic and then use the getObject functionality to get to the
Office objects in JAWS.
Take care,
Jonathan
On 28 December 2017 at 16:47, Paul Hunt <prhunt1@xxxxxxx> wrote:
Hello everybody. I checked the New Recipient and the Edit Recipientassumption is correct.
lists and they are not accessible with Narrator. I cannot reliably use
the JAWS cursor because JAWS doesn't speak what's under the JAWS
cursor in many office applications. It would be interesting to know
what happens in Narrator when the UIA elements expose their controls
properly. I assume that when Microsoft does this in an application it
automatically becomes accessible in Narrator but I'm not sure that my
Assuming that an application is accessible in Narrator but not inaccessible.
JAWS, what approach can we take to make it accessible while we wait
for VFO to make it a priority?
Thanks so much.
Paul
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx [mailto:jawsscripts-bounce@ ;
freelists.org] On Behalf Of Paul Hunt
Sent: Tuesday, December 26, 2017 10:32 AM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Making part of an application Accessible
Hello everybody. most of Microsoft Wordââ¬â¢s functionality is
There are three functions that are not. I believe that Microsoft mayand how to get to them.
have exposed the functionality but the screen readers (JAWS, Narrator
and NVDA) have not made these features accessible, probably because
they arenââ¬â¢t commonly used. How can I determine, from the FSUIA
object whether Microsoft has exposed these controls. Here are the features
1. Document Collaboration. To access this functionality, ccreate a
document, share it with another user, ask the user to make some
changes and save the document. Then access the document. It will show
which items the other user changed but you wonââ¬â¢t be able to see
them. Has Microsoft exposed this functionality even though the screen
Reader venders have not made it accessible? How can I determine
whether the controls have been exposed through the FSUIA object?
2. When using the Mail Merge facility, you can create a new
Recipients list. You access this interface with the Alt+R N key tip.
When you access this interface, you get an inaccessible table. Did
Microsoft expose this interface even though the Screen Reader venders
have not made it accessible? How can I confirm this FSUIA object?
3. 3. When using the Mail Merge function, you can edit an existing
recipient List. To access this interface, Access the Use Existing List
feature with the Alt+m,R,E key tip. Then browse for your list.
Finally, access the Edit Repient List with the Alt+M,D key tip. Did
Microsoft expose the controls of this interface? How can I confirm
this with the FSUIA object?
Finally, How will JAWS know when this interface has focus so that it
can react automatically?
Thanks so much.
Paul
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts