> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/product-reference/accessibility/webchat-webagent-dc2025.01.md).

# WebChat and WebAgent accessibility statement

Accessibility statement and keyboard navigation guidance for WebChat and WebAgent.

{% hint style="warning" %}
This accessibility statement was introduced in DC2025.01 and refers to WCAG 2.2. It does not specify a conformance level. For formal compliance requirements, confirm the applicable assessment and product version with AnywhereNow.
{% endhint %}

{% hint style="info" %}
Introduced in DC2025.01
{% endhint %}

AnywhereNow aims to provide accessible, inclusive, and user-friendly experiences. We are pleased to inform you that our **WebChat** and **WebAgent** applications comply with the **Web Content Accessibility Guidelines (WCAG)**, ensuring that we meet the needs of users with diverse abilities.

For AnywhereNow's Accessibility Statement also see: [AnywhereNow Accesibility Statement](https://www.anywhere.now/accessibility-statement)

* **WebChat**: Complies with WCAG 2.2 standards.
* **WebAgent**: Complies with WCAG 2.2 standards.

## Accessibility Features for WebChat and WebAgent:

1. **Contrast**: Both the Webchat and WebAgent provide sufficient contrast, ensuring readability for users with visual impairments.
2. **Screen Reader Support**: We implemented ARIA labels, semantic HTML, and other screen reader-friendly features to ensure our applications are accessible to users who rely on assistive technologies.
3. **Keyboard Accessible**: All functionality is available from a keyboard. Focusable components receive focus in an order that preserves meaning and operability.

## WebChat and WebAgent keyboard navigation:

* **Activate/Open**:
  * `ENTER`and `SPACE`keys activate buttons, checkboxes (check/uncheck), expand dropdown menus, open links, and open menus.
* **Tab Navigation**:
  * Pressing `TAB`moves focus to the next focusable element.
  * Pressing `SHIFT`+ `TAB`moves focus to the previous focusable element.
* **Arrow Navigation**: (navigate through the options within a list item or the items in a list)
  * `RIGHT/LEFT ARROW`: Moves focus **horizontally** to the next/previous focusable element when pressed.
  * `UP/DOWN ARROW`: Moves focus **vertically** to the next/previous focusable element when pressed.

## WebAgent Specific Navigation:

* **F6/Shift+F6**:
  * Pressing `F6`moves focus to the next focusable containers.
  * Pressing `SHIFT+F6` moves focus to the previous focusable containers within the application panels.
* **Modal**: When a modal is open, the focus is typically locked inside the modal to ensure that the user can only interact with the modal content until they make a choice, confirm an action, or close the modal. This prevents focus from shifting to other parts of the page behind the modal.

## WebChat Specific Navigation:

* **Auto-Close**: WebChat automatically closes when it loses focus.
* **Arrow Navigation**: WebChat supports scrolling when using arrow keys to navigate through content.
* **Arrows + Shift/ Arrows**:
  * `ARROW KEYS + SHIFT` enable the resizing of the WebChat window
  * `ARROW KEYS` enable the moving of the WebChat window


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/product-reference/accessibility/webchat-webagent-dc2025.01.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.