Using elementary OS’s On-Screen Keyboard and Accessibility Features
elementary OS is designed around a clean, focused desktop, but its accessibility tools are just as important as its visual style. Built-in options can make the system easier to operate without a physical keyboard, more comfortable to read, and more responsive to users who need extra time for clicks or keystrokes.
The most useful controls are collected in System Settings under Accessibility. Depending on the elementary OS release and the installed desktop components, the names and exact locations may differ slightly. Some options are available immediately, while others may require a package, an extension, or an application from AppCenter.
An on-screen keyboard can help with a failed laptop keyboard, touchscreen input, limited mobility, or occasional password entry. Accessibility settings can also reduce visual strain, make notifications easier to notice, and change how elementary OS interprets mouse and keyboard actions.
Finding The Accessibility Controls
Open the Applications menu, search for System Settings, and launch it. The Accessibility panel normally groups features into areas related to vision, hearing, and motor control. If your release uses a different layout, search Settings for terms such as “accessibility,” “keyboard,” or “large text.”
Before changing several options at once, enable one feature and test it for a few minutes. This makes it easier to understand what changed and to reverse a setting that does not suit your workflow. Some accessibility controls affect every application, while others are handled by individual apps.
A keyboard shortcut or pointer setting can also affect the way you open menus and switch windows. If a setting makes the desktop difficult to use, return to System Settings with the mouse or use the Settings search facility. Keeping a physical keyboard nearby is useful when experimenting with keyboard-related options.
Updates can move or rename controls. If an option described in an older guide is missing, check the release documentation and look in System Settings rather than assuming the feature has been removed. elementary OS’s interface changes gradually, and third-party accessibility tools may use different names from the built-in controls.
Using The On-Screen Keyboard
The on-screen keyboard displays a virtual layout on the desktop. You can activate keys with a mouse, touchpad, touchscreen, or another pointing device. It is useful for short typing sessions, entering a login, navigating a computer with a damaged keyboard, or avoiding repeated use of a painful physical keyboard.
In versions that provide the feature directly, open System Settings > Accessibility and look for a typing or keyboard section. Enable On-Screen Keyboard, Screen Keyboard, or a similarly named switch. The keyboard should appear when a text field is selected, although behavior can vary between applications and desktop versions.
The virtual keyboard is generally best for passwords, search terms, short replies, and commands typed occasionally. Long documents are slower because every character requires a pointer action. For extended writing, consider combining the on-screen keyboard with speech recognition, an external keyboard, or an alternative input device.
If your installation does not include a built-in virtual keyboard, an application such as Onboard may be available through AppCenter or the command line. Availability depends on the elementary OS release and its software sources. Install accessibility software only from a trusted source, and review its permissions before granting access.
A virtual keyboard may not appear on the login screen by default. The login manager has its own configuration and security restrictions, so desktop accessibility settings are not always applied before you sign in. If you need keyboard-free login, test that requirement separately and consider enabling automatic login only after assessing the security implications.
Making Typing Easier And More Predictable
Accessibility controls can change how elementary OS handles keys and pointer actions. Sticky Keys lets you press modifier keys such as Shift, Ctrl, or Alt one at a time rather than holding them together. This is helpful when a shortcut is physically difficult to perform.
Slow Keys adds a delay before a keypress is accepted. It can prevent accidental keystrokes caused by resting a finger on the keyboard. Bounce Keys ignores rapid repeated presses, which is useful when a key or switch produces duplicate input. These controls may be grouped under a typing assistance area.
Mouse Keys allows the numeric keypad, or another configured key group, to move the pointer. This is valuable when a mouse or trackpad is difficult to use. Pointer movement may feel slow at first, so adjust the speed and acceleration settings gradually rather than selecting the maximum immediately.
Some settings include an option to activate them through repeated key presses or shortcut sequences. Those shortcuts can be convenient, but they may also be triggered accidentally. Disable shortcut activation if the feature keeps turning on unexpectedly, especially on shared computers.
| Feature | Useful for | What it changes | Practical note |
|---|---|---|---|
| On-screen keyboard | Touch, pointer-only input, damaged keyboards | Displays clickable virtual keys | Best for short text entry |
| Sticky Keys | Difficulty holding several keys | Lets modifier keys work sequentially | Helpful for shortcuts |
| Slow Keys | Unwanted brief keypresses | Requires a key to be held longer | Test the acceptance delay |
| Bounce Keys | Repeated or tremoring presses | Filters rapid duplicate input | Useful with sensitive switches |
| Mouse Keys | Difficulty controlling a mouse | Moves the pointer with keyboard keys | Requires time to learn |
| Large Text | Small display text or visual fatigue | Enlarges interface text | May change layout spacing |
| High Contrast | Low-contrast interface elements | Makes foreground and background clearer | Check apps individually |
| Visual Alerts | Difficulty hearing sounds | Uses screen feedback for events | Useful with muted audio |
Improving Text Size And Visual Clarity
The Accessibility panel usually includes a large-text option that increases the size of interface text. This can make panel labels, menus, notifications, and dialog boxes easier to read without changing the monitor’s resolution.
For a broader change, open the display settings and check the scaling options offered by your release. Display scaling enlarges more interface elements than a text-only setting, but it may reduce the amount of information visible at once. A browser’s zoom control can then handle websites independently.
High contrast can help distinguish buttons, selected items, borders, and text from their backgrounds. It is especially useful when the default elementary OS theme feels too subtle. Some applications follow the system appearance closely, while others use their own interface and may need separate theme or contrast settings.
Pointer size is another worthwhile adjustment. A larger pointer is easier to locate on a high-resolution display or against a busy background. If your release offers pointer size and cursor theme controls, select a style with a strong outline and test it against both light and dark windows.
Night Light and display color controls address visual comfort rather than accessibility in the strict sense, but they can help during evening use. They should not replace appropriate brightness, room lighting, or professional advice for persistent eye discomfort. Text clarity and contrast remain more important than simply making the screen warmer.
Making Notifications Easier To Notice
Hearing-related accessibility options can provide visual feedback when an event normally produces a sound. A screen flash or other visual alert may help users who are deaf or hard of hearing, and it can also be useful when speakers are muted or headphones are disconnected.
Open the hearing section in Accessibility and look for visual notification controls. Depending on the release, the system may flash the entire screen, a window, or another visible element. Test alerts with a non-critical notification before relying on them for incoming calls, messages, or system warnings.
Notification behavior also depends on the application. A chat client, calendar, or email program may have its own alert settings, including banners, badges, sounds, and notification persistence. Configure both the system and the application if an important event needs more than one signal.
Avoid enabling every alert style at once. Large visual flashes can be distracting during video playback, gaming, or detailed work. A subtle banner combined with a persistent indicator is often easier to live with than repeated full-screen effects.
Combining Built-In Tools With Assistive Software
elementary OS’s native controls cover common needs, but users may need additional software for speech output, alternative input, switch access, magnification, or advanced virtual keyboard layouts. Linux accessibility applications often rely on technologies such as AT-SPI, GTK accessibility support, speech-dispatching services, and screen readers.
A screen reader converts interface text and application content into speech or Braille output. Orca is a commonly known Linux screen reader, although its installation and integration can vary across distributions and desktop versions. Before depending on it, test the applications you use most often, including the file manager, web browser, software center, and terminal.
A third-party virtual keyboard may offer word prediction, scanning modes, dwell-click input, customizable layouts, or automatic window placement. Those features can be more appropriate for motor-access needs than a simple clickable keyboard. Use the application’s documentation to understand startup behavior and whether it needs permission to monitor input.
Flatpak applications can have their own sandbox restrictions. An assistive tool may need access to windows, input devices, or accessibility interfaces that a sandbox limits. If a program behaves inconsistently, check its permissions and release notes rather than repeatedly reinstalling it.
Keep assistive applications updated and obtain them from AppCenter, official repositories, or the developer’s documented distribution channel. Accessibility software often handles sensitive screen and input information, so reliability and trust matter as much as convenience.
Troubleshooting Common Problems
If the on-screen keyboard does not appear, first confirm that the feature is enabled and that the cursor is inside a text field. Some applications use custom input controls that do not expose themselves correctly to the accessibility service. Try a text editor or the browser’s address bar to determine whether the problem affects the entire desktop.
A keyboard that covers the field you are typing into may need to be moved or resized. If the application window cannot be repositioned, maximize or restore it, then test whether the virtual keyboard docks differently. On a small display, reducing display scaling temporarily can create more usable space.
When Sticky Keys, Slow Keys, or Bounce Keys appear to stop working, check whether the active application captures keyboard input directly. Games, remote desktop tools, terminals with special key handling, and virtual machines may process input differently from standard GTK applications.
For a pointer that moves too slowly with Mouse Keys, adjust pointer speed and acceleration in the relevant settings panel. Also verify that Num Lock is in the state expected by the feature. On some layouts, the numeric keypad cannot control the pointer while it is being used for number entry.
If accessibility options reset after a restart, install pending system updates and check whether your session is saving settings correctly. A temporary guest session will not preserve personal preferences, and a damaged user configuration may require testing with a new user account. Record the original settings before resetting anything.
A Practical Setup For Everyday Use
Start with the smallest set of changes that addresses the immediate need. A user with limited keyboard control may begin with the on-screen keyboard and Sticky Keys. Someone dealing with accidental presses may need Slow Keys or Bounce Keys instead. Visual and hearing adjustments can then be added independently.
- Enable the on-screen keyboard and test it in a text editor, browser, and password field.
- Choose large text or display scaling based on readability, then check that important controls remain visible.
- Turn on Sticky Keys, Slow Keys, or Bounce Keys one at a time and adjust their activation behavior.
- Select a larger, high-contrast pointer and verify that it remains visible over light and dark windows.
- Configure visual alerts in the system and in essential applications such as messaging or calendar software.
Write down the settings that work well, including keyboard delay, pointer speed, text scale, and alert style. This makes it easier to restore the setup after reinstalling elementary OS or creating another user account. A short record is also useful when helping a family member or community forum participant.
Test the computer in the situations that matter most: signing in, connecting to Wi-Fi, opening files, entering a password, browsing the web, and shutting down. Accessibility is practical only when it works throughout the complete workflow, not merely inside System Settings.
The elementary OS community can provide useful release-specific guidance through forums and support discussions. When asking for help, include your elementary OS version, desktop session, affected application, and the accessibility feature involved. Avoid posting passwords, private documents, or screenshots containing personal information.
Explore the Accessibility panel in your elementary OS installation, enable one suitable feature, and test it in your daily workflow. Share reliable settings and solutions with the elementarynow community so other users can build a more comfortable, capable desktop.
