# Kiosk Accessibility

Accessible kiosks in service centers ensure all customers, including those with disabilities, can independently access services. Features like tactile interfaces and voice guidance enhance user experience, demonstrate inclusivity, comply with legal standards, and improve service efficiency.

This document describes Cubu Kiosk's accessibility features, scope, and configuration process.

Cubu Kiosks supports the following accessibility features:

* Accessible (High-contrast) Theme
* Keyboard Support
* IVR (Interactive Voice Response)

## Accessible Theme

When you configure Cubu, you can choose a Theme to control the kiosk's appearance and an Accessible Theme for when accessibility mode is used.

Customers can turn on the accessibility mode by using the accessibility switch on the kiosk. This changes the kiosk colors and increases the font size.

The following screenshot depicts a Kiosk running in Standard mode and in Accessible mode, using a high-contrast theme:

<div align="left"><figure><img src="/files/7pTsOe1GKR7UhAv5VQdO" alt="" width="375"><figcaption></figcaption></figure></div>

## Keyboard Support

Kiosks are typically operated using a touch screen, which is not usable for some people. \
Cubu Kiosk can be operated using a physical keyboard and supports all conventional navigation keys (i.e., tab, arrows, enter, etc.).

## IVR Mode

IVR (Interactive Voice Mode) provides the highest accessibility level, enabling visually impaired customers to use the kiosk by reading the screen content (text-to-speech) and making selections using a physically accessible numeric keypad.

When IVR is enabled for a kiosk, a voice message will be repeatedly played on the home page (this message can be customized using the Public App Profiles tool):&#x20;

> Welcome! To begin using the kiosk, please press 5 on the keyboard located at the bottom of the screen

The kiosk's home page will show the IVR activation key next to the accessibility mode:

<div align="left"><figure><img src="/files/RzTez9ZHsmCnRHoYRpPL" alt="" width="328"><figcaption></figcaption></figure></div>

When the IVR mode is enabled, selectable items are mapped to physical keys displayed on the screen and read out by the text-to-speech engine.

The following screenshot depicts a kiosk running in IVR mode, showing the service type selection page. Each clickable button is mapped to a keypad button, and the following message is played:

> Please select a service type.
>
> For Special Inquiry, press 1
>
> For Standard Inquiry, press 2
>
> To replay, press 0

<div align="left"><figure><img src="/files/HjCjV3AFBNyi8sU9Jqvy" alt="" width="329"><figcaption><p>Kiosk Page in IVR Mode</p></figcaption></figure></div>

### Accessible Keypad

An accessible numeric keypad typically includes the digits 0-9, an Enter/OK button (mapped to the Enter key), and a Cancel button (mapped to the Esc key). The keys are marked clearly with braille to aid visually impaired users in navigating and using the keypad effectively.

<div align="left"><figure><img src="/files/VVdo3yGwcG0CfRlpIyLh" alt="" width="306"><figcaption><p>Accessible Numeric Keypad</p></figcaption></figure></div>

{% hint style="info" %}
IVR Mode relies on a numeric keypad to interact with the kiosk. This mode is **unsupported for kiosk flows requiring** extended input (e.g., entering email, texts, dates, etc.).
{% endhint %}

### Customizing the IVR Texts

The Public App Profile tool allows customization of the texts read by the text-to-speech engine. Texts used for text-to-speech are marked with a speaker icon.

<div align="left"><figure><img src="/files/KqsBxo0BWlgdYnzRCGqt" alt="" width="375"><figcaption><p>Public Apps tool</p></figcaption></figure></div>

## More Information

{% content-ref url="/pages/8bio55UmsM2pXUV0G0N0" %}
[How To: Configure Accessible Kiosk with IVR](/guides/how-to-guides/kiosks/how-to-configure-accessible-kiosk-with-ivr.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cubu.com/guides/understanding-the-basics/kiosks/kiosk-accessibility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.