

Hello Quentin,
First of all, thank you for the update.
In previous NVDA roadmaps, especially in the medium-term development plans, you mentioned that you were working on enabling Microsoft natural voices to be used with NVDA. However, I could not see any work related to this in the new roadmap.
Is there any progress regarding the AI-based Microsoft voices? Or will there be any development in the future? Why was this development removed from the roadmap?
Thank you.
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAKsDpFhN1dBU1HRpGMhMYmR6Ki80-hmhjaGpoArFU2Na_z0D8A%40mail.gmail.com.
What happened to local AI model for ocr that you were supposed to introduced to nvda 2026.1? Aren't you supporting windows for arm devices?
A question was raised about the "AI-based Microsoft voices." Are these the same as "HD Voices" I have read about from Microsoft?This isn't a high priority. I'm fine with Microsoft Davie as it is today.
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
What happened to local AI model for ocr that you were supposed to introduced to nvda 2026.1? Aren't you supporting windows for arm devices?
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAODLbX%2BgY_NEzdz9yb7b7oJY40nVBdpo9W2r0d_2HW9pkJuJNw%40mail.gmail.com.
--
What happened to local AI model for ocr that you were supposed to introduced to nvda 2026.1? Aren't you supporting windows for arm devices?
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAODLbX%2BgY_NEzdz9yb7b7oJY40nVBdpo9W2r0d_2HW9pkJuJNw%40mail.gmail.com.