# 2.22.0

## Accessibility Enhancements

| Version      | 2.22.0     |
| ------------ | ---------- |
| Release Date | 2018-06-29 |

## Key features <a href="#id-20180629engage2.22.0accessibilityenhancements-keyfeatures" id="id-20180629engage2.22.0accessibilityenhancements-keyfeatures"></a>

This release introduces a range of accessibility enhancements based on feedback provided by the BTAA ITAG Engage subgroup, and primarily by Ohio State University.

## Details <a href="#id-20180629engage2.22.0accessibilityenhancements-details" id="id-20180629engage2.22.0accessibilityenhancements-details"></a>

### **App-wide changes**

* Engage now aurally indicates when its loading is complete.
* Engage now speaks "user menu" when user focuses the user menu.
* Fixed a bug where users could not select items in the user menu with the Enter or Space keys.

### **Terms view**

* In the Terms view, a Collection menu now operates properly as a menu. This means users can enter/exit the menu. When entered, the focus is set on the first menu item. The user may navigate with up/down arrows in the menu. Focus remains locked within the menu when using up/down arrows. Hitting the escape key exits the menu.
* When a user opens a book from the Term view, Engage will now announce that the book is open and focus is properly set.

### **Engage native reader**

* In the Engage native reader, tab ordering through the ToC is improved so that the user need not travel through the bookmarks tab to get to ToC items.
* In the Engage native reader, all controls that change the user's page now announce a change in page.
* Engage will now announce when the user lands in a page in the native reader from a link. This will apply to the following situations: (1) User navigates from a ToC item, (2) User navigates via page select control in native Reader, (3) User navigates with page left/right buttons in native Reader, (4) User selects a search results link (to a page).

### **All notes view**

* Form validation is now properly exposed to screen readers in the "Add note" workflow of the All notes view.
* The Engage native reader now includes a skip link to the All notes view for the course material.
* Engage will generate aural text to announce the effect of a user submitting or cancelling a form. This will apply to the following actions: Uploading materials, Adding external links, Copying materials from section to section, Adding a collection, Printing, Adding a note (All notes view), Editing a note (All notes view).
* When the user enters the All notes view, the number of notes presented is announced and focus is set on the first form control element (in the filtering panel).
* Whether the user enters the All notes view from the Terms view or the Reader, the user focus will now be set to the first form control element (in the filtering panel).
* When the user changes a filter control in the All notes view, aural text is generated to announce what filter was enabled or disabled and the resulting number of notes.
* When a user creates or edits a note in the All notes view, aural text is generated to assert that the action failed or was successful, depending on the outcome.

## Known Issues

None.


---

# 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://resources.unizin.org/products/content/unizin-engage/release-notes/2018-06-29-engage-2.22.0-accessibility-enhancements.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.