Screen reader issues in Firefox + NVDA

[danielweck]

Reported by Prashant Verma (DAISY Consortium)

(1) Table of Contents
When an entry in the TOC is clicked, the screen reader focus does not move automatically to the book text. When I try to go to the content window, the screen reader starts reading from the top of the current HTML file. The screen reader focus can be taken to the content window by pressing the single letter command “m” since it is in a different frame but even then the reading starts from top of page. When the user will want to move particularly to a sub-section, the TOC will not be helpful.
Currently, the user can move to all the headings in the current file by pressing the letter “h”. But when he wants to go to the next chapter which is a different file, he will have to again read the table of content from the very beginning. This is because there is no way of moving to the currently displayed section in the TOC. Therefore, work needs to be done for synchronizing the focus between the TOC and content both ways.

(2) Page navigation
(2.1)
Firstly, I think Readium should quickly implement the page list feature so that hard page breaks are also supported.
(2.2)
At present, when the next page or previous page button is pressed directly or using keyboard
shortcuts, the screen reader focus does not move to beginning of page text automatically. When I try to move to the text, the screen reader starts from beginning of current file.

(3) Settings dialog, slider controls
in the settings window the font and margin sliders are not accessible. When the sliders are adjusted, the screen reader does not read the changing values.