Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New option: don't stop SayAll during browse mode if moving betwen headings and other main html elements #1575

Closed
nvaccessAuto opened this issue Jun 17, 2011 · 5 comments

Comments

@nvaccessAuto
Copy link

Reported by drein on 2011-06-17 09:09
When pressing nvda+down arrow key in a web page and we then press the H key to move betwen headings, NVDA stops spekaing and we should re-press NVDA+down arrow.
User should have the option to choose the behaviour of the screen reader, since it can increase speed in some web page, especially for articles or reading news.

Blocked by #2766

@nvaccessAuto
Copy link
Author

Comment 2 by drein on 2011-06-17 15:38
Just to say that this feature can be applied not only to headings, but also for frames, the "n" key for text without links, blockquotes and 1-6 for specific headings.
Thank you for having put this ticket to trivial.

@nvaccessAuto
Copy link
Author

Comment 3 by drein on 2011-06-17 15:39
Changes:
Changed title from "New option: don't stop SayAll during browse mode if moving betwen headings" to "New option: don't stop SayAll during browse mode if moving betwen headings and other main html elements"

@nvaccessAuto
Copy link
Author

Comment 4 by briang1 on 2011-06-17 16:40
There have been a number of suggestions about reading web pages. I saw one which asked for auto say all on page loading to be optional, which then begs the question, what do you say when the page has loaded, and another to effectively leave caret on a line you want to hear update in real time, kind of say all but don't go anywhere!

The suggestion on this ticket would in effect like having the auto say all on page loading but from the element selected until it was interrupted in some way. This could be good for well structured web sites. So how to impliment all this withut causing confusion? You would want them to be toggleable, presumably?
Just a few thoughts

@nvaccessAuto
Copy link
Author

Comment 5 by nvdakor on 2013-11-25 11:45
Hi,
I believe this has been introduced in 2013.3 (forgot the ticket number for this).
Thanks.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2013-11-26 00:29
Thanks. Duplicate of #2766.
Changes:
Added labels: duplicate
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant