New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support Microsoft Office Publisher #4653
Comments
Comment 1 by nvdakor on 2014-11-30 17:50 |
Comment 2 by blindbhavya on 2014-11-30 17:54 |
Comment 3 by nvdakor on 2014-11-30 18:03 |
Comment 4 by blindbhavya on 2014-12-01 16:15 |
@bhaviahshah are you still having this issue? |
The elements on a page are still fully inaccessible with NVDA 2019.2.1 and Microsoft Publisher 2010 on Win7x64. And the Mouse Tracking only reads the complete line through the total length of a page, even if their content is part of separate text fields, which aren't linked together. |
I have a project in my company that requires the use of publishers on office 365. |
cc: @Qchristensen, @feerrenrut maybe you can have a look on this, if the time permits. In corporate environments publisher is quite common software. Were there any conversations with Microsoft on this program sofar? |
No, I state that the problem can be solved by screen readers.
|
Please don‘t make such controversial statements without details. Do you have some technical details prooving that Publisher exposes this properly to screen readers? If not, then please let‘s continue the discussion preferably with meaningful comments. Thanks.
|
Reported by blindbhavya on 2014-11-30 12:17
Hi,
NVDA does not support Microsoft Office Publisher 2007 well enough to be usable, thats the very first impressions I have got, because of the following inaccessible parts:
Open a blank Microsoft Office Publisher 2007 file, and Tab around. In some palces, NVDA won't read anything on a Tab.
JAWS, does read those though, which are the Close Catalog button, Geting Started button, and some other things.
Please make nVDA support Microsoft Office publisher as well, especially since in the last few versions you guys have greatly enhanced accessibility for other Microsoft Office applications.
By the way, there may be other parts of this program that mya be inaccessible, please someone investigate.
The text was updated successfully, but these errors were encountered: