Windows Mobile 6.5 Bluetooth Braille Support

Windows Mobile 6.5 did not feature native, out-of-the-box support for refreshable Braille displays. Instead, it enabled Braille accessibility through third-party mobile screen readers paired with the operating system’s standard Bluetooth stack. By establishing a virtual serial connection between the phone and external hardware, third-party accessibility applications translated screen content into Braille patterns and received input commands from the display.

The Role of Third-Party Screen Readers

Because Microsoft did not integrate a system-level Braille engine into Windows Mobile 6.5, users relied on specialized commercial accessibility software. The dominant platform was Mobile Speak, developed by Code Factory. These screen reader applications sat between the Windows Mobile operating system and the hardware, monitoring the graphical user interface, active text fields, system notifications, and menu states to extract text for Braille rendering.

Bluetooth Serial Port Profile (SPP)

The physical communication relied on the Bluetooth Serial Port Profile (SPP), which Windows Mobile 6.5 supported natively. Connecting an external Braille display involved several steps:

  1. The user placed the Braille display into pairing mode.
  2. Windows Mobile’s Bluetooth manager detected the display and established an authenticated link via a PIN code.
  3. The operating system mapped the Bluetooth device to an outgoing virtual COM port (such as COM6 or COM7).
  4. Within the screen reader’s settings, the user selected the assigned COM port and designated the specific Braille display manufacturer and model (e.g., HumanWare, Freedom Scientific, Handy Tech, or Baum).

Real-Time Translation and Drivers

The screen reader maintained proprietary or open-source translation tables (such as Liblouis) alongside specialized device drivers for dozens of Braille terminals. When text appeared on the Windows Mobile screen, the software translated the characters into Grade 1 (uncontracted) or Grade 2 (contracted) Braille code. It then converted those codes into the specific data packets expected by that terminal’s hardware driver and pushed the data over the virtual COM port. The refreshable pins on the display would instantly raise to reflect the on-screen text.

Bidirectional Control and Navigation

The Bluetooth SPP link was strictly bidirectional. In addition to outputting text, the screen reader processed incoming keystrokes from the Braille terminal's input keys or Perkins-style keyboard.

Users could navigate the Windows Mobile 6.5 interface entirely through the external display. Specific key chords or routing keys mapped directly to Windows Mobile actions, such as pressing the Start key, opening context menus, scrolling lists, tapping simulated touch areas, or typing text directly into SMS messages, emails, and Word Mobile documents.