# 2.20.5

## Accessibility Update

| Version      | 2.20.5     |
| ------------ | ---------- |
| Release Date | 2017-08-02 |

## Key features <a href="#id-20170802engage2.20.5accessibilityupdate-keyfeatures" id="id-20170802engage2.20.5accessibilityupdate-keyfeatures"></a>

This minor release introduces a set of accessibility enhancements proposed by Ohio State University. We thank the OCIO Accessibility Analysts and Digital Accessibility Center at Ohio State for their recommendations and dialog. Also, this release introduces a few bug fixes.

## Details <a href="#id-20170802engage2.20.5accessibilityupdate-details" id="id-20170802engage2.20.5accessibilityupdate-details"></a>

* The "Home" button is no longer labeled “Term” but “Home,” for users of adaptive technologies (AT).
* In the "Home" view, adds H3 headings for Section collections.
* Users can now open, navigate, and escape from the analytics modal with keyboard interactions.
* When the user changes a page in the Engage Reader, the focus is maintained on the button they used to change the page.
* The “Go to” text input in the Engage reader is properly labeled as such for adaptive technology users.
* After users conduct a search, the focus is set on the first search result. If no search results are returned, the focus is set on the text input of the search form.
* Descriptive labels to the external search links on the search results page have been added for AT users.
* The title attribute is removed from the previous and next buttons in the reader.
* Fixes a bug in which notes in the Reader jumped or stretch given the right combination of user actions.

## 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/2017-08-02-engage-2.20.5-accessibility-update.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.