> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/ux-and-design/accessibility.md).

# Accessibility

We believe great products should be usable by everyone, regardless of ability. 1kosmos is designed and built to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

***

### What WCAG 2.2 AA means

WCAG 2.2 (a W3C Recommendation since October 2023) organizes accessibility requirements around four principles: content must be **Perceivable, Operable, Understandable, and Robust**. Level AA is the conformance level most widely adopted by organizations and referenced by regulations such as the ADA (US), Section 508, and the European Accessibility Act / EN 301 549.

WCAG 2.2 builds on 2.1 with additional success criteria, including improvements for focus visibility, touch target sizes, dragging alternatives, consistent help, and more accessible authentication.

### Finding your way around: the command palette

Every page in AdminX is reachable from the keyboard using the command palette, a global search available from the header.

**To open it:**

* Click **Search** in the top-right of the header, or
* Press **⌘K** (Mac) / **Ctrl+K** (Windows)

Start typing to filter across top-level pages, including Dashboard, Directory, Users, Applications, Authentication, Reports, Settings, Verification, and Workflows. Use the arrow keys and **Enter** to jump to a result without touching the mouse. Your search history is retained for 7 days.

### Accessibility improvements&#x20;

| Where                                    | What changed                                                                                                                                                            |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Session Details                          | A Copy to clipboard button next to the session data view lets you copy details without a mouse, and is reachable by keyboard shortcut.                                  |
| Session Events                           | Keyboard navigation now moves focus through events in the correct order.                                                                                                |
| Sidebar icon tooltips                    | Tooltips stay visible on hover and can be dismissed, instead of disappearing as the pointer moves onto them.                                                            |
| Sidebar expand control                   | Announced by screen readers within the navigation region, in the correct reading order.                                                                                 |
| Verification Flows / Templates           | New default ID proofing templates apply automatically to all tenants. A new Edit template option is available directly on the Verification Flows page.                  |
| Forms, analytics, calendar, pagination   | Form fields are labeled, charts are operable using a keyboard, and selected states meet color contrast minimums.                                                        |
| Share via text                           | A new Country Code label was added alongside the phone number field.                                                                                                    |
| Document scan and selfie capture screens | Updated to a clean white background across templates, replacing the previous green gradient and dark capture screen. Visual update only; no change to the capture flow. |

### How we support accessibility

* **Keyboard navigation** — All interactive elements are reachable and operable using a keyboard alone.
* **Command palette** — A keyboard-first **Search** control in the AdminX header opens a command palette. Type to find any top-level page in the console and go straight to it, without navigating through menus.
* **Screen reader support** — Semantic markup and ARIA labels provide a meaningful experience with assistive technologies such as NVDA, JAWS, and VoiceOver. Focus order follows the logical structure of each page, including navigation regions and controls such as the sidebar expand control.
* **Color contrast** — Default themes meet the 4.5:1 (text) and 3:1 (large text / UI) contrast minimums, and our branding tools help you preserve contrast in custom themes.
* **Visible focus indicators** — A clear focus state shows keyboard users where they are as they move through forms, tables, charts, and the ID proofing capture flow.
* **Persistent, dismissible tooltips** — Tooltips on sidebar icons and other controls remain visible on hover and can be dismissed, instead of disappearing as the pointer moves onto them.
* **Accessible forms, charts, and data views** — Form fields carry proper labels, charts are operable using a keyboard, and selected states across tables, calendars, and pagination controls meet color contrast minimums.
* **Responsive layout** — The header, navigation, verification screens, forms, analytics, calendar, pagination, and the ID proofing capture flow adapt responsively across screen sizes.


---

# 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://docs.1kosmos.com/identity-verification/ux-and-design/accessibility.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.
