AACSpeakHelper is a small tool that enables you to\

• Take text written in a Windows AAC application

• If you need to - Translate it using a choice of online translation systems

• and if you need to - Speak that text using a range of online or new offline speech models supporting not currently supported by commercial providers

It is good if you

• Want to set up a AAC system for someone speaking in a language not currently supported by solutions available

• If you have a client who wants to communicate to some people using a language they aren't familiar with. For example speaking to carers who are don't communicate using the communication aid users language or need to speak to family members who only speak in a language that they dont have a understanding of that written form

What its not good for

• Reading or saving long streams of text (eg reading a book aloud)

• If you want to use with a piece of software you cant copy the text from a message bar

• You really have to use iOS, Android or something else

1. Language translation and speech output

Imagine you are a Kurdish speaker with limited English skills residing in a care facility. AAC Speak Helper bridges you and your caregivers, translating Kurdish text into English. Moreover, it supports people who need to speak languages less commonly supported by TTS technology.

1. Language not supported by current commercial solutions

If you speak Urdu - either as a bilingual speaker or as your primary language it can be difficult to find the perfect AAC system to meet your needs

AAC Speak Helper is a lightweight Windows executable. It can be called from any AAC app on Windows that can run external programs.

AAC Speak Helper reads the text once the text is copied to the clipboard (using Ctrl+C). Depending on the configuration settings, it either translates the text using the selected service, speaks it aloud, or reads it. There are additional features, such as putting intonation (or style) onto some voices. We provide a CLI configuration tool to set up the application. The main application, though, has no interface.

Download the installer from our latest release. You click on the link under "assets" for the file named AACSpeakHelper-v2.2.8.exe (or whatever number is there)

Alternatively you will find the current most release on the Ace Centre Website

AACSpeakHelper ISNT a SAPI Speech engine. What this means is it is not seen by your AAC Software as a voice you would pick in your regular settings screen. We have to do some things to get this to work. And note you will have to be comfortable editing your software.

In short you need to:

• Add a button to copy the message bar (writing area)

• Then, have an action on this button to call the executable found at %UserProfile%\AppData\Local\Programs\Ace Centre\AACSpeakHelper\client.exe

Run the installer. Click through the options. At the end you can choose to run the applications - we recommend running these.

If you don't check these boxes - you can run them from your desktop or Start Menu. The applications you need to run are:

1. AACSpeakHelperServer - this runs in the background in your task bar

2. Configure AACSpeakHelper CLI - this allows you to configure the setup you need using a command-line interface

So we are not providing here software Gridsets/Pagesets of Keyboards for different languages.

If you want a client to write in the language of this TTS system (not use translate) You have to

• Find a keyboard layout the client is familar with in the correct script.

• Copy and paste the characters needed into a Gridset/Pageset that you need. Remember to not put spaces behind the characters

• This is painstaking. Please consider sharing your work so others can benefit.

As this is a quick prototype, it may have some issues. For issues regarding connectivity or functionality, please note that Azure, Google Cloud and translation services require an online connection. If you have any questions, suggestions, or contributions, please create a pull request or donate.

Common Feature requests

• Offline Translation. Although possible with NLLB (Meta) its not easy to do all the language pairs we potentially need.

• The key feature is to make the integration easier. This is actually best done if it was a system wide voice rather than all software having to integrate different providers. So how do we do it? See our roadmap

• ElevenLabs access.

• Offline Azure/Google etc voices. Although advertised as kind of possible its not without limitations (notably not all voices are available like this from Microsoft and particularly not those that are of high need becauser we dont have much language support)

• It works on Python 3.10 or 3.11. The dependencies aren't well covered on all other versions (and there are a lot!)

• We use a GitHub action to build the application (see workflow here.)

Building the Application

Development Testing

# Test the server
uv run python AACSpeakHelperServer.py

# Test the client (in another terminal)
uv run python client.py

# Test CLI configuration tool
uv run python cli_config_creator.py

Building for Windows

Azure TTS

• You first need an Azure subscription - Create one for free.

• Create a Speech resource in the Azure portal.

• Your Speech resource key and region. After your Speech resource is deployed, select Go to resource to view and manage keys. For more information about Azure AI services resources, see Get the keys for your resource

Creating a service account for OAuth 2.0 involves generating credentials for a non-human user, often used in server-to-server interactions. Here's how you can create OAuth 2.0 credentials using a service account for Google APIs:

Create a Service Account:

1. Go to the Google Cloud Console: Visit the .

2. Create a New Project: If you don't already have a project, create a new one in the developer console.

3. Enable APIs: Enable the APIs that your service account will be using. For example, if you're using Google Drive API, enable that API for your project.

• In the Google Cloud Console, navigate to "IAM & Admin" > "Service accounts."

• Click on "Create Service Account."

• Enter a name for the service account and an optional description.

1. Create and Download Credentials:

• On the next screen, you can grant the service account a role in your project. You can also skip this step and grant roles later.

• Click "Create Key" to create and download the JSON key file. This file contains the credentials for your service account.

• Keep this JSON file secure and do not expose it publicly.

1. Use the Service Account Credentials:

• In your code, load the credentials from the JSON key file. The credentials can be used to authenticate and access the APIs on behalf of the service account.

1. Grant Required Permissions:

• If you skipped assigning roles during the service account creation, you can now grant roles to the service account by navigating to "IAM & Admin" > "IAM" and adding the service account's email address with the appropriate roles.

Blood, sweat and tears

We have

1. A pipe server (AACSpeakHelperServer.py)

   1. Reads in a config dict from settings.cfg

• Have you just downloaded a new model? Give it a little while.. The pipe service doesnt report back when the model has downloaded and ready so the GUI tool just reports back ready. It should cue up your request though so it might take a little while

• Preview just says "Hello world" and runs client. If it is set to translate it may be sending the incorrect text. Try using translate and match the language you are trying to preview

Ummm its stopped working

AACSpeakHelper now uses a modern, intuitive configuration system with positive boolean logic. This guide explains how to configure it effectively.

New Configuration System

After installation, you need to configure the application. There are two main ways to configure AACSpeakHelper:

1. CLI Configuration Tool - Use our command-line configuration tool Configure AACSpeakHelper CLI (recommended)

2. Manual Editing - Edit the settings file by hand using a text editor

The easiest way to configure AACSpeakHelper is using our CLI configuration tool. You can find Configure AACSpeakHelper CLI in your start menu after installation, or run it directly from the installation directory.

The CLI tool provides an interactive menu with the following options:

1. Configure TTS Engine - Set up your Text-to-Speech engine and voice

2. Configure Translation - Set up translation settings and language pairs

3. Configure Transliteration - Set up script conversion settings (e.g., Latin to Devanagari)

When you select option 1, you'll be able to choose from several Text-to-Speech engines:

Sherpa-ONNX (Recommended for most users)

• Offline TTS engine that works without internet

• Supports a large range of languages not supported by other systems

• Good balance of quality and performance

• No API keys required

Azure TTS (High quality, requires API key)

• Microsoft's cloud-based TTS service

• Excellent voice quality and natural speech

• Requires Azure Speech Services subscription and API key

• Supports many languages and voices

Google TTS (High quality, requires API key)

• Google's cloud-based TTS service

• High-quality voices with natural intonation

• Requires Google Cloud TTS API credentials

• Wide language support

Google Trans TTS (Free, limited quality)

• Free TTS using Google Translate

• No API key required but limited quality

• May have usage restrictions

Other Premium Engines Available:

• ElevenLabs - Premium quality voices, requires subscription

• PlayHT - High quality voices, requires subscription

• AWS Polly - Good quality, requires AWS account

When configuring a TTS engine, you'll be prompted for:

Voice ID - The specific voice to use (varies by engine and language) Rate - Speech speed (0 = normal, negative values = slower, positive = faster) Volume - Audio volume (100 = normal, 50 = quieter, 150 = louder) Save Audio File - Whether to save audio files to disk for caching and reuse Bypass TTS - Skip text-to-speech entirely (useful for translation-only mode)

When you select option 2 from the main menu, you can configure translation settings:

GoogleTranslator (Free, limited usage)

• Free translation service using Google Translate

• May have usage limits or temporary blocks with heavy use

• Good for testing and light usage

Microsoft Translator (Requires API key)

• High-quality translation service

• Requires Azure Translator subscription

• More reliable for production use

Other Translation Providers Available:

• DeepL (Premium quality, requires API key)

• Yandex Translator

• Baidu Translator

• LibreTranslate

Enabled - Enable or disable translation entirely (true/false) Source Language - The language of your input text (e.g., "en" for English) Target Language - The target language for translation (e.g., "ps" for Pashto) Replace Clipboard - Whether to replace clipboard content with translated text

When you select option 3 from the main menu, you can configure transliteration settings:

Transliteration converts text from one script to another while maintaining the same language. For example, converting Latin script "namaste" to Devanagari script "नमस्ते" (both are Hindi, just different scripts).

Enabled - Enable or disable transliteration entirely (true/false) Language - The language for transliteration (Hindi, Arabic, Bengali, etc.) From Script - The source script (e.g., "Latn" for Latin) To Script - The target script (e.g., "Deva" for Devanagari) Replace Clipboard - Whether to replace clipboard content with transliterated text

• Arabic (ar) - Latin ↔ Arabic script

• Bengali (bn) - Latin ↔ Bengali script

• Gujarati (gu) - Latin ↔ Gujarati script

Transliteration requires Azure Translator credentials:

• Azure Translator subscription key

• Azure resource region (e.g., "uksouth", "eastus")

These can be configured in your settings file or through environment variables.

If you prefer to edit configuration files directly, you can manually edit the settings.cfg file.

For installed versions: Navigate to %AppData%\Ace Centre\AACSpeakHelper in File Explorer to find the settings.cfg file.

For development versions: The settings.cfg file is located in the project root directory.

You can edit the configuration file using any plain text editor (Notepad, VS Code, etc.). The file uses INI format with sections and key-value pairs.

You can create multiple configuration files for different use cases:

Command Line Usage:

Distribution to End Users: You can create pre-configured settings files and distribute them to users. This is useful for organizations that want to deploy AACSpeakHelper with specific settings.

[App] - Application settings

• collectstats - Whether to collect anonymous usage statistics

[processing] - Processing pipeline settings

• pipeline - Order of processing steps (e.g., "translate,transliterate,tts")

[translate] - Translation settings

• enabled - Enable translation (true/false)

• source_language - Source language code (e.g., "en")

• target_language - Target language code (e.g., "ps")

[transliterate] - Transliteration settings

• enabled - Enable transliteration (true/false)

• language - Language code for transliteration (e.g., "hi")

• from_script - Source script code (e.g., "Latn")

[tts] - Text-to-Speech settings

• enabled - Enable TTS (true/false)

• engine - TTS engine name (e.g., "azureTTS")

• save_audio - Save audio files (true/false)

[TTS] - Text-to-Speech settings

• engine - TTS engine name (e.g., "azureTTS", "Sherpa-ONNX")

• bypass_tts - Skip TTS entirely (True/False)

• save_audio_file - Cache audio files (True/False)

Engine-specific sections (e.g., [azureTTS], [googleTTS])

• Contains API keys, credentials, and engine-specific settings

This tool supports a multitude of languages provided through Azure and Google Cloud. For a detailed list, please refer to the respective sections below.

WARNING

Please note. If you use any online TTS system, the data is sent to a server and sent back. These services do not store this data, but it is up to you to check this and how it may work against your own IG policy. The app does have a feature of 'caching' data, too - but this is not sent to Ace or anyone else. It's all on the device.

Languages by Azure

For the most up-to-date list see the list here

Languages by Azure (Online)

First up, check the table below for Languages officially supported by the software you are using. You can also use this as a tool to find which apps support a language you are interested in. Be careful. Some languages write in different scripts. Check the script that the TTS engine expects.

MindExpress

• All versions of anReader 4.2.8 support both 32-bit and 64-bit versions of Windows OS.

• It is recommended that Windows is updated and the latest system patches are installed.

• On Windows 10 and Windows 11, only the latest version of NVDA is currently supported, with other screen readers minor problems may occur in the operation of anReader.