1 Reply Latest reply on Oct 1, 2015 2:43 PM by a C student

    NVDA and Adobe Digital Editions - poor user experience

    city_chicken

      Hello,

       

      I am trying to help a visually impaired student read a DRM-protected eBook within Adobe Digital Editions using NVDA.  The student normally uses Zoom Text but this is not compatible with the eBook's DRM, so he has downloaded NVDA, which Adobe recommends for use with ADE.

       

      He is able to get NVDA to read the content of the eBook, but the user experience is very poor:

       

      - When reading, NVDA does not announce any page number, chapter, or other location marker within the book to let the student know where he is in the text

      - If the student pauses NVDA (to take a note, for example), then re-starts it, NVDA begins reading again but does not announce where it is reading from, so the user has no point of reference. 

      - In some cases the student reports that when re-started, NVDA begins reading from the start of the book again, which is confusing, and makes it nearly impossible to get back to where they were, as no location was announced during reading to begin with.

       

      Here are some details that may be of use:

      - Student runs a Windows machine using Windows 8.1

      - Student is reading fully searchable (non-image) eBook PDFs which includes page numbers and fully navigable table of contents

       

      Adobe recommends use of NVDA with Adobe Digital Editions for accessibility.  Please provide some suggestions for this student to improve the usability of your product.

       

      Thank you.

        • 1. Re: NVDA and Adobe Digital Editions - poor user experience
          a C student Level 3

          Some of these problems seem more likely due to NVDA configuration or possibly the need for NVDA user training. On the PDF side, the eBook is probably not optimally tagged (that is, PDF/UA and/or WCAG 2.0 compliant), or may not be tagged at all in which case NVDA would be inferring tags. Page numbers are not usually included in the tagged reading structure, as they would interrupt the reading flow and are not really meaningful in an audio presentation of the content. Chapter numbers and/or titles should be read as headings. Manual remediation by someone with knowledge and experience in the process would fix any problems on the PDF side, but doing so can be time consuming.