Do what one of the main purposes of AI is. Ask it to solve the problem.
Ask it to present the answer with numbers accessible to screen-readers
and the problem will be solved, at least it has been when I've asked
that this be done.
AI may give good information or not, in all sorts of situations,
including asking for something to be done to solve a problem, so real
care must be taken in evaluating answers, but not using AI in ways like
this disregards one of the main points of AI.
Gene
On 4/24/2026 2:16 AM, Yong Shing wrote:
> Hi all,
>
> I have been facing this issue for some time now.
>
> When using NVDA, on AI chat platforms e.g Gemini, when the response
> contains MATH or equation or certain numbers, NVDA won't read them. The
> same issue described here.
> <
https://github.com/nvaccess/nvda/issues/18157> I installed MathCap
> addon, but it doesn't fix the issue either.
>
> What solutions are available so far? If you can share, it would be great!
>
> Thank you!
>
> Regards,
> Yongshing
>
> --
> ***
> 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
> <
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
> <mailto:
nvda-users+...@nvaccess.org>.
> To view this discussion visit
>
https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAH5wdDa0X3sbqOhEqnZe5bCUg15DB2-g089s8FVefbfODpcwfQ%40mail.gmail.com
> <
https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAH5wdDa0X3sbqOhEqnZe5bCUg15DB2-g089s8FVefbfODpcwfQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.