{"id":1242,"date":"2018-04-26T19:58:13","date_gmt":"2018-04-26T19:58:13","guid":{"rendered":"http:\/\/pressbooks.library.ryerson.ca\/pwaa\/?post_type=chapter&p=1242"},"modified":"2022-12-16T15:57:49","modified_gmt":"2022-12-16T15:57:49","slug":"chromevox-screen-reader","status":"publish","type":"chapter","link":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/chapter\/chromevox-screen-reader\/","title":{"raw":"ChromeVox Screen Reader","rendered":"ChromeVox Screen Reader"},"content":{"raw":"We will introduce you to ChromeVox, the screen reader we will be using, early on, so you have plenty of opportunity to practice using it. It will be a key tool used in auditing the accessibility of web content, and will be used in the activity for this unit.\r\n\r\nFor day-to-day screen reader testing, ChromeVox (particularly the ChromeVox plugin for the Chrome web browser) is our screen reader of choice because of its simple installation and configuration, ability to work across computer platforms, and the fact that it\u2019s free and open source.\r\n
\r\n\r\nTechnical: <\/strong>One reason ChromeVox works well for accessibility testing is its good support for ARIA. We will cover ARIA in greater detail in the unit\u00a0Other Accessibility Standards<\/a>. ARIA is still a relatively new technology, and as of late 2019, it is still being supported inconsistently across available screen readers. When developing for the Web, do use ARIA as it is intended to be used as documented in the ARIA Specification, and test it with ChromeVox.\r\n\r\nYou will still want to test with JAWS or perhaps NVDA, as these are most likely to be used by blind users. You may, however, find that what works in ChromeVox does not work with the other screen readers. So, for the time being, it may be necessary to provide workarounds when developing custom web elements, so they will work across technologies, with the assumption that these other technologies will catch up eventually.\r\n\r\n<\/div>\r\nWhile a relatively small number of screen reader users currently use ChromeVox, it is a highly effective tool for developers when testing web content. Also, ChromeVox is tailored to work with elements of Google Drive<\/a><\/strong>, so even for users of other screen readers, ChromeVox may be preferable when compiling Google Docs, Sheets, and Slides.\r\n
\r\n\r\nToolkit:<\/strong> Visit the Chrome store while using the Chrome web browser to install the ChromeVox screen reader<\/a>. It will be a key element of your Toolkit.\r\n\r\n<\/div>\r\n
Key Point: <\/strong>Though we recommend using ChromeVox for activities that follow, and as a tool that works well for screen reader testing while accessibility auditing, you are free to use other screen readers if you prefer.<\/div>\r\nThe videos below will help show you how to install and begin using ChromeVox.\r\n\r\nVideo: Installing ChromeVox<\/a><\/strong>\r\n\r\n[embed]https:\/\/youtu.be\/MC8reXDktM8[\/embed]\r\n\r\nVideo: ChromeVox Demo<\/a><\/strong>\r\n\r\n[embed]https:\/\/youtu.be\/qnM75U8LSxY[\/embed]\r\n\r\n\u00a9 Google Open Online Education.\u00a0Released under the terms of a Standard YouTube License. All rights reserved.<\/span>\r\n

ChromeVox Testing and Associated Key Commands<\/h2>\r\n
Key Point: <\/strong>Download the ChromeVox Keyboard Commands [docx]<\/a>, outlined in the table below, print it, and have it beside you when completing the activity in this unit. Also be sure you have set the ChromeVox modifier key*, described in the following line, or you are going to have difficulty with the activity.<\/div>\r\n* The ChromeVox modifier key (i.e., Cvox) is set in Chrome\u2019s Settings > Extensions > ChromeVox Options, typically set to Alt or Ctrl.\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Task<\/th>\r\nTask Description<\/th>\r\nKeyboard Command<\/th>\r\n<\/tr>\r\n<\/thead>\r\n
Default Reading<\/td>\r\nWhen a webpage loads, ChromeVox will read the element that takes focus on the page. Use the Cvox + arrow keys to read through content. Listen to the spoken output and note any inconsistencies from what one might expect to hear based on what is visible on the screen.<\/td>\r\nCvox + up and down arrows<\/td>\r\n<\/tr>\r\n
Tab Navigation<\/td>\r\nWhen a page has loaded, press the Tab key to navigate through operable element of the page like links and forms. Listen to the output when these elements are in focus, and note any elements that are clickable, but not focusable with the keyboard.\r\nAlso listen for hidden elements such as bypass links or other elements that are not visible but are read aloud by ChromeVox.<\/td>\r\nTab, Shift Tab<\/td>\r\n<\/tr>\r\n
Navigate Through Headings<\/td>\r\nStep through all the headings on a page. Note whether all headings are announced as expected. Note the heading level announced. Are they sequenced to create semantic structure (i.e., nested in the proper order)?<\/td>\r\nCvox + L + H then up\/down arrows<\/td>\r\n<\/tr>\r\n
Navigate Through Landmarks<\/td>\r\nStep through the landmarks, key navigation points on a page. Are all areas of the page contained in a landmarked region? Note any missing Landmarks.<\/td>\r\nCvox + L + ; (semi-colon) then up\/down arrows<\/td>\r\n<\/tr>\r\n
List Links<\/td>\r\nList the links and navigate through them using the arrow keys, listen for meaningfulness, or listen for context when links are otherwise meaningless.<\/td>\r\nCvox + L + L then up\/down arrows<\/td>\r\n<\/tr>\r\n
Navigate Through Forms<\/td>\r\nNavigate to forms on a page, then press the Tab or F keys to listen to each of the fields. Are fields announced effectively, including required fields?<\/td>\r\nCvox + L + F then up\/down arrows<\/td>\r\n<\/tr>\r\n
Navigate Through Tables<\/td>\r\nNavigate to Tables on a page, press Enter to go to a table, press up\/down arrow keys to move through cells in sequence (left to right, top to bottom), press Ctrl + Alt + arrow to move to adjacent cells, press Ctrl-Alt and 5 on the number pad to list column and row headers where applicable. Note whether header cells are read or not. Are fieldset labels announced, where applicable?<\/td>\r\nCvox + L + T then up\/down arrows\r\nthen Enter to select Table\r\nCvox + arrow to move within table\r\nCvox +TH to announce headers<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n ","rendered":"

We will introduce you to ChromeVox, the screen reader we will be using, early on, so you have plenty of opportunity to practice using it. It will be a key tool used in auditing the accessibility of web content, and will be used in the activity for this unit.<\/p>\n

For day-to-day screen reader testing, ChromeVox (particularly the ChromeVox plugin for the Chrome web browser) is our screen reader of choice because of its simple installation and configuration, ability to work across computer platforms, and the fact that it\u2019s free and open source.<\/p>\n

\n

Technical: <\/strong>One reason ChromeVox works well for accessibility testing is its good support for ARIA. We will cover ARIA in greater detail in the unit\u00a0Other Accessibility Standards<\/a>. ARIA is still a relatively new technology, and as of late 2019, it is still being supported inconsistently across available screen readers. When developing for the Web, do use ARIA as it is intended to be used as documented in the ARIA Specification, and test it with ChromeVox.<\/p>\n

You will still want to test with JAWS or perhaps NVDA, as these are most likely to be used by blind users. You may, however, find that what works in ChromeVox does not work with the other screen readers. So, for the time being, it may be necessary to provide workarounds when developing custom web elements, so they will work across technologies, with the assumption that these other technologies will catch up eventually.<\/p>\n<\/div>\n

While a relatively small number of screen reader users currently use ChromeVox, it is a highly effective tool for developers when testing web content. Also, ChromeVox is tailored to work with elements of Google Drive<\/a><\/strong>, so even for users of other screen readers, ChromeVox may be preferable when compiling Google Docs, Sheets, and Slides.<\/p>\n

\n

Toolkit:<\/strong> Visit the Chrome store while using the Chrome web browser to install the ChromeVox screen reader<\/a>. It will be a key element of your Toolkit.<\/p>\n<\/div>\n

Key Point: <\/strong>Though we recommend using ChromeVox for activities that follow, and as a tool that works well for screen reader testing while accessibility auditing, you are free to use other screen readers if you prefer.<\/div>\n

The videos below will help show you how to install and begin using ChromeVox.<\/p>\n

Video: Installing ChromeVox<\/a><\/strong><\/p>\n