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
Virtual buffer, ability to ignore refresh content in a page. #4342
Comments
Comment 1 by jteh on 2014-07-30 01:55 If we didn't update browse mode, the content you read with NVDA wouldn't reflect the content on the page, which means you wouldn't be able to activate links in that content, etc. We can't simply stop the page from updating, and if we did, you wouldn't be able to access half the content it is offering. |
Comment 2 by aleskis (in reply to comment 1) on 2014-07-30 07:46 Please, try this link and give me a strategy to navigate quietly:
|
Comment 3 by jteh on 2014-07-30 07:57 There is simply no reliable way to suppress updates like this. The fact that the original information disappears might prevent you from navigating, but if we don't refresh, then the information you're navigating is probably already invalid and you certainly won't be able to activate anything inside it. I'm happy to consider this a request to disable live regions using the setting for reporting of dynamic content, but I don't think disabling of browse mode updates is something we can consider. |
Comment 4 by briang1 on 2014-07-30 12:32 Maybe they are just utilising things for jobs they were never intended for, but we do need to live in the worrld as it is, not as it really should be or was originally intended to be. |
Reported by aleskis on 2014-07-29 16:55
On certain webpage like in the sharepoint CRM, the content is permanently actualised. In the case of progress bar or quick carouzel, the reading by the synthetizer it permanently interrupted by the refreshing informations.
More annoying, the NVDA focus slide in the content page, causing high difficulties for reading line by line.
You can see an example here:
http://lechal.com/accessibility.html
The text was updated successfully, but these errors were encountered: