Getting started with the NVDA screen reader
Automated tools for checking website accessibility (such as WAVE, AChecker or the aXe Chrome extension) are often the starting point to find and correct accessibility violations. Another important option to include in your accessibility testing toolset is a screen reader and keyboard, to help understand how a visitor with visual or motor disabilities might experience the library's website. A free choice for this is NonVisual Desktop Access (usually abbreviated as NVDA).
To get started using NVDA, download it to your Windows computer. It can be installed and used without admin rights (though enlisting an admin for the install let me use it without having to accept the terms of use every time) or even saved to a portable USB flash drive to run on different computers. When you start it up, it begins reading what you have on screen out loud. Switch to a web browser, and it will read the web pages you visit. This video includes how-to's and some demonstration:
NVDA has a Help menu and highly detailed user guide, but WebAIM's "Using NVDA to Evaluate Web Accessibility" is the quick-start guide I wish I'd started with. I use these tips a lot for testing web pages with NVDA:
- F5 refreshes the page and starts reading from the beginning (in case you get lost).
- The Insert key is the default special "NVDA key" for using the keyboard to navigate with NVDA.
- NVDA key + S lets you toggle between having speech mode on, off, or "beeps mode" (so you can have NVDA on for a website you're testing, but turn it off to type an email where it would be distracting for NVDA to spell out what you're typing letter by letter).
With a little practice, you'll be able to test how your libary's website performs with a screen reader and keyboard. Despite the learning curve, it's a solid step you can take to identify problems, obstacles, and annoyances that can be fixed to help all patrons benefit from the services your library provides.
Comments
You can follow this conversation by subscribing to the comment feed for this post.