EBSCO Reader by EBSCO Information Services
- Reading System EBSCO Reader
- Vendor EBSCO Information Services
- Assistive Technology: NVDA
- OS: Windows
- Browser: Chrome
- Tested with Braille: No
- Tested with Screenreader: Yes
- Input type: Keyboard
Results for Basic Functionality: 60%
Last updated: 3 October 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 | |
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 | User would generally have an account prior with an institution such as a library or university, and then sign in using those credentials. The sign in process is navigable and functional. |
file-210 | Open content | Open the Fundamental Accessibility Test book in the reading system. | Pass | |
file-310 | Access list of available content in the reading system | Check if you can navigate inside the bookshelf. | Pass | |
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 Table of Contents is navigable, though it can feel dense when moving through it with a screen reader. |
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 | |
nav-110 | Navigate content by pages | Check if you can navigate the content by pages. | Fail | This failed due to the button labeling error making this unclear. All pages of a chapter are displayed and navigable with headings, and have displayed page numbers. However, the buttons labelled Go To Previous Page and Go To Next Page seem to actually navigate by chapter. |
nav-210 | Navigate forward and backward through reflowed content | Use any control or command to navigate forward and backwards in the book content. | Pass | |
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. | Pass | There isn't a "where am I" command, but page numbers, section headings, and the book's title are all available on the reader page at any given time. |
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 | Within Content Searching and Search Results are both navigable. At the first time of testing, this functionality was not working, only throwing up this warning "Unable to load results. Please try again.". However, I attempted this again and it worked. Unsure what the error stemmed from. |
nav-510 | Move across chapters without using TOC | Check if you can move across chapters without having to use the Table of Contents. | Fail | This both fails and passes. There is functionality allowing the user to navigate by chapter outside the Table Off Contents, but the buttons that allow this are labelled Go To Previous Page and Go To Next Page. |
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 | Unable to find bookmark or highlight feature. |
anno-110 | Review and navigate Bookmarks or Highlights | Check if you can review and navigate Bookmarks or Highlights. | Fail | |
anno-210 | Add a note | Add a Note at this location in the book. Provide a few lines of text in the Note. | Fail | Unable to find notes feature. |
anno-310 | Review and navigate Notes | Check if you can review and navigate Notes. | Fail |
Results for Non-visual Reading: 87.5%
Last updated: 4 October 2024
Test book used: Fundamental Accessibility Tests: Non-Visual Reading, version 2.0.0 .
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 | This tester could not test if the text remained on screen. |
reading-110 | Stop and resume reading at the same reading location | 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 | |
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 | |
reading-310 | Image alternate text reading | Ensure that the alternate text for the image is available. | Pass | |
reading-420 | Footnote Reading | This tests the usability and functionality of footnotes. The markup includes the semantics that the reference is to a note,which could be announced to the reader. The destination could be a footnote or an endnote and announced to the reader. The link back to the original position has the semantics that it is a backlink and could also be announced to the reader. | Pass | The footnote is announced as "link 1", and the return link is announced as "link [return to note reference 1 about Chief Joseph]". When using the arrow keys the return link is announced as "footnote link [return to note reference 1 about Chief Joseph]". |
reading-510 | TTS allows pause for indicating 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 | |
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 | |
reading-710 | Navigate between internal hyperlinks | Check if you can navigate between internal hyperlinks. | Pass | |
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 | |
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 | |
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 | |
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 | |
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 | |
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. | Pass | |
reading-1410 | MathML Reading | The block and inline math expressions below are in the MathML format. We want to determine that the Assistive Technology (AT) identifies the math and enables the detailed exploration of the math with the chosen AT. | Fail | The screen reader is silent when navigating to the equations. All that the screen reader can see are white space, like when you press the space bar. The first equation has one white space character, while the second has two white space characters. |
reading-1510 | TTS Change Languages Automatically | Screen readers and other Assistive Technology that use TTS should be able to detect language changes marked in XHTML content. A screen reader should be able to be configured to automatically change the TTS speaking language when it encounters a language change in the XHTML. This test contains English, German, French, and Italian. | Fail | The screen reader does not change dialects after downloading language packs and configuring settings to change dialect/language when supported. |