With the Simple Orca Plugin System (SOPS) you can extend the functionality of the Orca screen reader ( ). It offers the possibility to add plug-ins in nearly any programming language in an easy way. The settings for the plug-ins are controlled via the filename.
Install the package AUR.
To setup the plug-in system for the current user, run:
- The Installation path. This contains the default plug-ins, the documentation,the plugin loader and the administration tools:
- The path for user plug-ins is:
- The following path is used for all enabled (active) plug-ins. All plug-ins in that folder will be loaded, if they are valid:
The tools are located in the "tools" folder beneath the installation directory. The following command enables/activates a plug-in, but you have to rename the filename to create a shortcut and pass a command to the plug-in:
$ ./ensop <pluginname>
The command to disable and unload a plug-in is:
$ ./dissop <pluginname>
Both commands basically just create or delete links in
~./.config/SOPSP/plugins-enabled and make the plug-ins executable. You have to configure the plug-ins manually.
Restart Orca to reload the plug-ins after changes.
SOPS also provides a plug-in manager, it is available after the installation.
To open the plug-in manager use
orca+ctrl+p while Orca is running.
It can be used to activate, deactivate, install or configure plug-ins.
Orca gets re-started automatically after closing the plug-in manager.
Structure of the filename
The shortcut, plug-in type and preference of a plug-in are controlled by its filename.
The descriptive part of the filename has to be separated from the preferences part with
The commands, modifier and the key has to be separated by
Run a plug-in
There are two different ways to run a plug-in:
- shortcut (See #Modifiers/ Shortcuts)
- exec run once when the plug-in loads. (See #Commands/ Preferences)
If none of those are present. the plug-in does not load. There are some more #Commands/ Preferences to control the behaviour of a plug-in.
With modifiers you can set different shortcut combinations for a
You always have to press the Orca-modifier.
The order of the three modifier keys does not matter:
controlis the modifier for the
ctrlkey on the keyboard
shiftis the modifier for the
shiftkey on the keyboard
altis the modifier for the
altkey on the keyboard
key_<key>defines the basic shortcut that is used for the plug-in, maybe together with the defined modifiers (example_plugin__-__key_d.sh uses
Only a few combinations of modifiers are valid. Those are predefined by Orca. Valid combinations are:
control + alti.e.
shift + alti.e.
key_<key> you can use every alphanumerical key.
Preferences for plug-ins are called commands. A command defines the action to pass to the plug-in. With commands you control the behaviour of the plug-ins. You may add more than one command. The order of the commands does not matter. You can use them mostly for all kinds of plug-ins.
startnotifyannounces "start <description>" before the plug-in is executed. It is useful as feedback for plug-ins with longer progress times. (all plug-ins)
stopnotifyannounces "finish <description>". This is useful as feedback for plug-ins with no output. (all plugins)
blockcalldo not start the plug-in in a thread. Be careful, as this locks Orca until the plug-in is finished. By default, plug-ins each run in a dedicated thread. (all plug-ins)
errorannounces returned errors. (all plug-ins)
supressoutputignores the output of STDOUT. This is useful for plugins that may have a UI and do not pass output to STDOUT. (sub process plug-in only)
parameters_<parameter1> [parameter2] [parameter3]...passes the parameters to the plug-in. (sub process plug-in only)
execrun the plug-in once while loading it. Mostly useful as advanced-plug-in. (all plug-ins)
loadmoduledoes not load as a sub process plug-in but loads it as advanced plug-in. (advanced plug-in only)
Plugin name__-__startnotify__+__control__+__alt__+__key_n.shRun with
orca+ctrl+alt+nand announce the start of the process.
orca+shift+mand announce the finishing. Does also read occurring errors .
Plugin_Name__-__exec.pyRun once at starting Orca.
Types of plug-ins
Basically there are two different types of plugins.
Sub process plug-ins
Sub process plug-ins are simple plug-ins and the default type.
They may be any type of application or script that writes to STDOUT or STDERR.
Orca executes the plug-in, reads from STDOUT/ STDERR and announces the result to the user, when the defined shortcut is pressed or the plug-in is executed via
exec while starting screen reader.
- Execution permission
exechave to be defined in the filename.
Say "Hello World when pressing
#!/bin/sh echo "Hello World"
Those type of plug-ins are loaded with the spec.loader.exec_module. you can load them by using
loadmodule in the filename. They are fully included into Orca as soon as it starts.
Advanced plug-ins are more powerful, because you are able to work in the Orca context. They are mostly similar to the
See also for "real" Orca scripting:
https://wiki.gnome.org/Projects/Orca/FrequentlyAskedQuestions/CustomizingOrca[dead link 2020-04-03 ⓘ]
- Correct code written in python3
loadmodulein the filename
exechave to been defined in filename
Configure Orca to speak/braille the word "bang" instead of the "!" while loading the plug-in.
import orca.orca orca.chnames.chnames["!"] = "bang"
You can also host plug-ins, making them available for installation via the plug-in manager.
If you want to Host plug-ins, read: