EBSCO Reader by EBSCO Information Services
- Reading System EBSCO Reader
- Vendor EBSCO Information Services
- Assistive Technology: JAWS 2020
- OS: Windows
- Browser: Chrome
- Tested with Braille: No
- Tested with Screenreader: Yes
- Input type: Keyboard
Results for Non-visual Reading: 85.71%
Test book used: Fundamental Accessibility Tests: Non-Visual Reading, version 1.0.0 . These results are based on an older test book revision. A newer version of Non-visual Reading is available.
Summary
Generally, screen reader access with JAWS worked well. Navigating with internal hyperlinks took the focus to the start of the chapter, which is really problematical for navigating end notes and supplementary content such as extended descriptions. It was not possible to copy text.
Test ID | Name | Description | Result | Notes |
---|---|---|---|---|
reading-010 | Initiate "read from here" | Focus on the beginning of a paragraph or a sentence and initiate reading. Reading should continue until interrupted by the user or at the end of the current document, e.g. current chapter. The text being read should preferably remain in view, but this is not a requirement to pass the test. | Pass | The read all commands reads the document till end of chapter |
reading-110 | Stop and resume reading | Initiate reading from any point in the book. Stop reading and note the last read position. Initiate reading again and check if reading starts at the last read location. | Pass | Worked as expected |
reading-210 | All text should be read in the proper order | Sample text has been provided to test the reading order. The Paragraph 2 should be read after Paragraph 1. Note that visually Paragraph 2 is placed to the left of Paragraph 1 but it is second in the reading order. | Pass | Worked as expected. |
reading-310 | Image alternate text reading | Ensure that the alternate text for the image is available. | Pass | |
reading-410 | Change reading speed | It should be possible to adjust (increase/decrease) the speed of reading. This test should be performed using the Assistive Technology being used for accessibility evaluation. | Pass | Worked as expected. |
reading-510 | TTS allows pause for headings, paragraphs, list items, etc | The user should be able to identify the difference between content items such as headings, paragraphs or list items by sufficient pauses in the TTS reading or appropriate formatting in the Braille device. | Pass | All screen reader table navigation works as expected. |
reading-610 | Navigate between the cells, rows and columns in the table | Check if you can navigate between the rows and columns of the table | Pass | All screen reader table navigation works as expected. |
reading-710 | Navigate between internal hyperlinks | Check if you can navigate between internal hyperlinks. | Fail | The screen reader focus does not return to the correct location from a back link. The back link returns to the beginning of the chapter. This presents a major problem if extended descriptions are included using the back link technique. |
reading-810 | Move to the next block item | Check if you can move to the next available page element e.g. paragraph, image or table by using a common key/gesture like swipe right, down arrow etc. | Pass | These screen reader commands worked as expected. |
reading-910 | Navigate by characters | Check if it is possible to navigate to next and previous character in the book text by way of any command or gesture. | Pass | These screen reader commands worked as expected. |
reading-1010 | Navigate by words | Check if it is possible to navigate to next and previous word in the book text by way of any command or gesture. | Pass | These screen reader commands worked as expected. |
reading-1110 | Navigate by lines | Check if it is possible to navigate to next and previous line in the book text by way of any command or gesture. | Pass | These screen reader commands worked as expected. |
reading-1210 | Navigate the content by headings | Check if you can move to the next and previous headings in this book without using the Table of Contents. | Pass | These screen reader commands worked as expected. |
reading-1310 | Select and copy text | Reading systems should provide the ability to copy pieces of text that could be used for notes, in quotations, or to facilitate searching terms contained in the book. In some cases, this could be achieved using an AT such as a screen reader, for instance with a dedicated cursor or other procedures. | Fail | Text could not be copied. |
Results for Basic Functionality: 73.33%
Last updated: 1 July 2024
Test book used: Fundamental Accessibility Tests: Basic Functionality, version 2.0.0 .
Test ID | Name | Description | Result | Notes |
---|---|---|---|---|
file-010 | Operating system/Platform accessibility: | If you are using a hardware device, it can be started independently and essential accessibility for starting and exiting applications is available. | Pass | With JAWS loaded in Windows start Chrome browser and navigate to the site. |
file-110 | The reading system can be activated independently | If you are using a reading app that requires you to create an online account then the complete getting started process should be accessible. | Pass | No issues faced in login |
file-210 | Open content | Open the Fundamental Accessibility Test book in the reading system. | Pass | The test books were preloaded in the catalog. It was possible to select the intended book from the list. |
file-310 | Access list of available content in the reading system | Check if you can navigate inside the bookshelf. | Pass | The bookshelf is accessible with JAWS. The screen reader focus is not synchronized with display. The control to view next set of books needs to be used manually. JAWS can read the book titles which are not on screen. |
nav-005 | The table of contents in the app presents the content hierarchy | Check if the table of Contents is accessible and its hierarchy is presented correctly by the reading system | Pass | The TOC is presented as a nested list, the main sections can be collapsed and expanded with keyboard and JAWS. |
nav-010 | Navigate to chapters through the Table of Contents | Check if you can navigate to a section by using the table of contents. | Pass | The screen reader focus lands at the desired location after selecting a topic in TOC. |
nav-110 | Navigate content by pages | Check if you can navigate the content by pages. | Fail | Print page navigation not supported. |
nav-210 | Navigate forward and backward through reflowed content | Use any control or command to navigate forward and backwards in the book content. | Pass | Screen reader text navigation keystrokes are working as expected. |
nav-310 | Read navigation information | Use the "Where am I?" or any other similar command available in the reading system and check if you can get information about your current position in the book. | Fail | Percentage read or current page number cannot be determined without losing reading position. The name of current section can be checked from the JAWS headings list [INS+F6]. |
nav-410 | Perform a search, review the search results | Perform a search, review the search results and navigate to the selected search result in the content. | Pass | |
nav-510 | Move across chapters without using TOC | Check if you can move across chapters without having to use the Table of Contents. | Pass | The next and previous chapter button can be used. Ideally keystrokes should be provided for easy access. |
anno-010 | Add a Bookmark or Highlight | Some reading systems may have a Highlight feature in place of Bookmarks. The tests for Bookmarks may then be performed with Highlights. | Fail | Bookmark feature not provided. |
anno-110 | Review and navigate Bookmarks or Highlights | Check if you can review and navigate Bookmarks or Highlights. | Fail | Bookmark feature not provided. |
anno-210 | Add a note | Add a Note at this location in the book. Provide a few lines of text in the Note. | Pass | Notes could be added but highlighting is not supported. |
anno-310 | Review and navigate Notes | Check if you can review and navigate Notes. | Pass | The notes could be read and edited. The navigation to page containing the note is not entirely predictable. |