![]() ![]() Are fields announced effectively, including required fields? Navigate to forms on a page, then press the Tab or F keys to listen to each of the fields. List the links and navigate through them using the arrow keys, listen for meaningfulness, or listen for context when links are otherwise meaningless. Are all areas of the page contained in a landmarked region? Note any missing Landmarks.Ĭvox + L + (semi-colon) then up/down arrows Step through the landmarks, key navigation points on a page. Are they sequenced to create semantic structure (i.e., nested in the proper order)? Note whether all headings are announced as expected. Listen to the output when these elements are in focus, and note any elements that are clickable, but not focusable with the keyboard.Īlso listen for hidden elements such as bypass links or other elements that are not visible but are read aloud by ChromeVox. ![]() When a page has loaded, press the Tab key to navigate through operable element of the page like links and forms. Listen to the spoken output and note any inconsistencies from what one might expect to hear based on what is visible on the screen. Use the Cvox + arrow keys to read through content. When a webpage loads, ChromeVox will read the element that takes focus on the page. * The ChromeVox modifier key (i.e., Cvox) is set in Chrome’s Settings > Extensions > ChromeVox Options, typically set to Alt or Ctrl. 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. ![]() Key Point: Download the ChromeVox Keyboard Commands, outlined in the table below, print it, and have it beside you when completing the activity in this unit. Also, ChromeVox is tailored to work with elements of Google Drive, so even for users of other screen readers, ChromeVox may be preferable when compiling Google Docs, Sheets, and Slides. While a relatively small number of screen reader users currently use ChromeVox, it is a highly effective tool for developers when testing web content. 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. You may, however, find that what works in ChromeVox does not work with the other screen readers. You will still want to test with JAWS or perhaps NVDA, as these are most likely to be used by blind users. 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. ARIA is still a relatively new technology, and as of late 2019, it is still being supported inconsistently across available screen readers. We will cover ARIA in greater detail in the unit Other Accessibility Standards. Technical: One reason ChromeVox works well for accessibility testing is its good support for ARIA. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |