Skip to content
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

Jump to bottom

getting the cc and bcc fields to speak in Microsoft Outlook #864

Closed
nvaccessAuto opened this issue Aug 27, 2010 · 6 comments
Closed

getting the cc and bcc fields to speak in Microsoft Outlook #864

nvaccessAuto opened this issue Aug 27, 2010 · 6 comments
Assignees
@michaelDCurran
Labels
bug
Milestone
2011.2

Comments

@nvaccessAuto
Copy link

Reported by ManuelRamos on 2010-08-27 21:13
I'm not using Microsoft outlook at this time. However, I've been told that it is working well with NVDA. But, I've heard Lusitan users telling me that it would be exccelent getting the cc and bcc fields to speak. In fact, when sending mails, "from", "to", "subject" and "message" fields are being read well. So, I'm requesting that cc and bcc fields can be read in Microsoft Outlook.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-08-27 22:08
Definitely not for 2010.2.

Do you mean in the composer or the message reader?
Changes:
Milestone changed from 2010.2 to 2010.3

@nvaccessAuto
Copy link
Author

Comment 2 by ManuelRamos on 2010-08-28 08:42
I mean in the composer.

@nvaccessAuto
Copy link
Author

Comment 3 by mdcurran on 2010-12-02 02:32
Changes:
Milestone changed from 2011.1 to near-term

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2011-06-09 07:15
Changes:
Milestone changed from near-term to 2011.3

@nvaccessAuto
Copy link
Author

Comment 5 by mdcurran on 2011-06-10 02:57
Fixed in a216b8c. Or if not, I mis-understood the problem. Please reopen if its not fixed
Changes:
Milestone changed from 2011.3 to 2011.2
State: closed

@nvaccessAuto
Copy link
Author

Comment 6 by mdcurran on 2011-06-10 03:03
sorry, #421 is really the ticket fixed by a216b8c. Perhaps this ticket is a duplicate. If it is in deed fixed by that change then it is. If its not fixed, it should be reopened.

@nvaccessAuto nvaccessAuto added this to the 2011.2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelDCurran michaelDCurran

Labels
bug
Projects
None yet
Milestone
2011.2
Development

No branches or pull requests
2 participants
@michaelDCurran @nvaccessAuto