> For the complete documentation index, see [llms.txt](https://ebay.gitbook.io/oatmeal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ebay.gitbook.io/oatmeal/screen-reader.md).

# Screen Reader Methods

## Methods

* [NVDA Smoke Test](/oatmeal/screen-reader/nvda-smoke-test.md)

## Screen Reader Testing Strategy

### Desktop

Testing must be done in order of the following screen reader/browser combinations.

1. JAWS with IE on Windows
2. [NVDA](https://www.nvaccess.org/download/) with Firefox on Windows
3. VoiceOver with Safari on Mac OS

### Mobile

Use the native screen reader and the following browsers.

* Android: TalkBack with Chrome
* iOS: VoiceOver with Safari

### Screen Reader Verbosity

Screen readers typically allow users to customize what details their screen reader will announce. Unless otherwise specified, all screen reader testing methods assume default verbosity settings.

## Screen Reader Set Up

* [NVDA Set Up](/oatmeal/screen-reader/nvda.md)
* For VoiceOver, just [Fix Safari Tabbing](/oatmeal/help/fix-safari-tabbing.md)

## Other Screen Reader Resources

* [WebAIM: Using NVDA to Evaluate Web Accessibility](http://webaim.org/articles/nvda/)
* [WebAIM: Using VoiceOver to Evaluate Web Accessibility](http://webaim.org/articles/voiceover/)
* [WebAIM: Using JAWS to Evaluate Web Accessibility](http://webaim.org/articles/jaws/)
* [The Paciello Group: Shut Up JAWS](https://developer.paciellogroup.com/blog/2017/07/shut-up-jaws/)
* [Aural UI of the Elements of HTML](https://thepaciellogroup.github.io/AT-browser-tests/)

### Videos

* [Deque: Accessibility Testing with the NVDA Screenreader](https://www.youtube.com/watch?v=Vx1vSd5uYS8)
* [Google: Screen Reader Basics: NVDA](https://www.youtube.com/watch?v=Jao3s_CwdRU)
* [Google: Screen Reader Basics: VoiceOver](https://www.youtube.com/watch?v=5R-6WvAihms)


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ebay.gitbook.io/oatmeal/screen-reader.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.