> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/functional-specification/its_navigator_keypad.md).

# its\_navigator\_keypad

{% columns %}
{% column width="33%" %}
![](/files/LVIXOkRtelQVWrrCUgUl)
{% endcolumn %}

{% column %}
**Description**

**Payment**

Customer can insert, tap, or swipe a card. Basket shows the number of items added from the amount entry screen.

\
**Accessibility**

Vision Accessibility menu can be accessed by tapping the yellow “eye” button.

When the accessibility mode option is enabled, the customer or merchant can double tap anywhere on the screen or press the tactile accessibility button on the side of the terminal to turn on accessibility mode. Accessibility mode can also be turned on by following the options inside Vision Accessibility menu.

When the assistance mode option is enabled, the customer or merchant can tap the “eye” button, then select “Color / Large Text” option to chose the best contrast color for the payment screens. For the remainder of the transaction, the screens will have the background color that is chosen.

Once the accessibility/assistance mode is turned on, the screen prompts will be read aloud to the customer.

\
**Note**

Yellow “eye” button will be present only when accessibility or assistance options are enabled in Navigator configuration.

The confirmation mechanism selected here (double-tap on the screen vs. use of the tactile accessibility button) will remain in effect through the rest of transaction flow.

\
**Configuration Parameters**

`Navigator.CustomerStartAccessibleModeEnabled` - Enables the accessibility mode

`Navigator.CustomerStartAssistantModeEnabled` - Enables the assistant mode

`Navigator.DefaultChimeVolumeLevel` - Minimum chime volume level
{% endcolumn %}
{% endcolumns %}

\---


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/functional-specification/its_navigator_keypad.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.