Skip to the content.
Silhouette of Dr. Jacob Bolotin, text reads National Federation of the Blind Bolotin Award Winner

User Guide

Advice on Choosing a Voice

In NVDA, you have a choice of using different synthesizers. This is found in NVDA Preferences:Settings... followed by choosing Speech. There are usually at least three choices: eSpeak NG, Microsoft Speech API, Windows OneCore voices. All synthesizers work, but the Windows OneCore voices don’t support speaking “a” properly and the other options should be used. In particular, the Microsoft Speech API are a good substitute for the OneCore voices.

Information for MathCAT users

MathCAT supports a number of options to control speech, braille, and navigation. These are described below. Not all options are currently supported. The current state of support for an option is listed with the option and a ✓ is used before the option as a quick reference to indicate at least partial support for that option.

Note: in NVDA, the options can be set by using the MathCAT preferences dialog. This is accessed by going to the NVDA preferences, choosing “Preferences”, and then “MathCAT settings…”. The settings are divided into three categories: Speech, Navigation, and Braille. This division is reflected in the documentation below.

MathCAT supports multiple modes of navigation. The means to begin navigating and end navigating will differ depending on the AT you are using. See the list below. The commands/key-strokes accepted by MathCAT are the same as those accepted by MathPlayer and are listed in this document. The documentation describes many useful ways to navigate math. For those who just want to get started:

To start navigation:

MathCAT’s navigation is the same in Word and in a browser.

While navigating an expression, “control+c” copies the MathML for the current node in NVDA.

Option List

The options are listed below. Most options allow only a limited set of values and those are indicated in the options. The default value is given in [brackets].

Speech Options


ClearSpeak has a number of options. These were designed for authors to use, but can also be set by a user although they are not that useful.

Braille Options

Braille codes often have author-definable characters. MathCAT provides some options:

The UEB Guide to Technical Material says to normally treat Fraktur and DoubleStruck as Script. Here we provide an option to specify a transcriber-defined typeform prefix indicator instead. Note: here are prefixes for 1st - 5th: “⠈⠼”, “⠘⠼”, “⠸⠼”, “⠐⠼”, “⠨⠼”

The characters for Vietnam that are definable is still be discussed. Likely, they will change some.

Other Options

MathCAT cleans up bad MathML. Numbers are frequently improperly marked up in MathML. In order to clean them up correctly, MathCAT needs to know locale information about what characters might be used to separate digit blocks and what characters are used a decimal separator. Typically this is set by AT based on the country code in the document. However, that may not be given and only the language code is given and so AT needs to guess based on that.