> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/other/accessibility.md).

# Accessibility

Accessibility-related controls, limitations, and support options in Ango Hub.

Ango Hub includes keyboard shortcuts and controls for adjusting how assets and annotations appear. This page describes those controls, limitations to consider when planning a project, and how to report an accessibility barrier.

The features below apply to Ango Hub's web labeling editors. Available controls vary by editor, project configuration, and deployed version. See [System Requirements](https://docs.imerit.net/other/system-requirements.md) for browser requirements.

## Keyboard Shortcuts

Click on the *Keyboard* icon in the labeling editor to view the available shortcuts. These include actions such as saving, undoing and redoing changes, selecting tools, and navigating annotations.

Some editors also provide shortcuts for moving or resizing existing annotations. See [Keyboard and Mouse Shortcuts](https://docs.imerit.net/other/keyboard-and-mouse-shortcuts.md) for details and restrictions.

Shortcuts reduce the need to repeat some mouse actions, but do not provide a complete keyboard-only workflow. Drawing and editing annotations can still require a mouse or another pointing device.

## Display and Playback Controls

| Editor | Available controls                                                                                                                                                                                     | More information                                                                                                                                          |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Image  | Zoom in, zoom out, or fit the image to the screen. From the quick settings, adjust image brightness, contrast, and color inversion, as well as annotation opacity, point radius, and border thickness. | [Image Labeling Editor](https://docs.imerit.net/labeling/labeling-editor-interface/image-labeling-editor.md#quick-settings-menu)                          |
| Text   | Press **Shift + T** to display class names next to text entities. This lets you identify their classes by name as well as by color.                                                                    | [Text Labeling Editor](https://docs.imerit.net/labeling/labeling-editor-interface/text-ner-labeling-editor.md#display-entity-class-names-next-to-classes) |
| Audio  | Pause and resume playback, change playback speed and volume, replay a selected segment, and zoom the waveform.                                                                                         | [Audio Labeling Editor](https://docs.imerit.net/labeling/labeling-editor-interface/audio-labeling-editor.md#bottom-bar)                                   |

Image brightness, contrast, inversion, and zoom controls adjust the asset being labeled. They do not change the contrast or text size of the surrounding interface.

## Limitations and Assistive Technology

Many annotation tasks involve inspecting visual content, positioning shapes, selecting text spans, or listening to audio. The controls described above do not remove those task requirements. For example, a waveform or spectrogram does not provide a text equivalent of spoken content.

This page does not establish compatibility with specific screen readers, speech-input tools, or other assistive technologies. Before starting a project that depends on these tools, evaluate the complete workflow with representative assets, including opening tasks, creating and editing annotations, answering classifications, and submitting work. Include the people who will use the workflow in that evaluation.

Project instructions, imported assets, and embedded content also affect accessibility. Project managers should provide clear instructions and any text alternatives needed for the task, and discuss barriers with their iMerit contact before assigning work.

## Accessibility Assessments and Supplier Reviews

This page provides product information for accessibility reviews. It is not an Accessibility Conformance Report (ACR) and does not make a claim of conformance with the Web Content Accessibility Guidelines (WCAG).

An ACR documents evaluation results against accessibility criteria and may be prepared using the [Voluntary Product Accessibility Template (VPAT)](https://www.itic.org/policy/accessibility/vpat).

If you need an ACR, a completed VPAT, or evidence for a supplier questionnaire, contact your iMerit representative to confirm which documentation is available for the product version and deployment you intend to use. Include the required standard, assessment date range, and workflows in scope.

## Report an Accessibility Barrier

Use the [Customer Support](https://docs.imerit.net/other/customer-support.md) channels or contact your iMerit representative. If you cannot use the support portal or in-app form, contact your representative directly.

Please include:

* The page or editor where the barrier occurs and the task you were trying to complete.
* Steps to reproduce the problem, what you expected, and what happened instead.
* Your browser, operating system, and any assistive technology, including their versions.
* Whether the issue prevents you from completing the task and any workaround you have found.

Response times follow your support agreement. See [Customer Support](https://docs.imerit.net/other/customer-support.md) for details.

*Last updated: 28 October 2026.*


---

# 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.imerit.net/other/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.
