|
Re: loss of shortcut keys
hello.
toggle quoted messageShow quoted text
i had this issue for awhile, but thanks God, i found a workarround for it. when nvda keyes dont work, do the following. 1. press nvda plus q. 2. nvda exit dialog options are in the background. 3. press alt plus tab to find the dialog box. 4. press scape to close it. in normal cases, when you press nvda plus q, nvda dialog box is available and you can navigate immediately instead of using alt tab.
On 1/22/21, Don H <lmddh50@adams.net> wrote:
Running NVDA 2020.4 beta 4 on a Win 10 20h2 system. --
By God, were I given all the seven heavens with all they contain in order that I may disobey God by depriving an ant from the husk of a grain of barley, I would not do it. imam ali
|
|
|
|
Re: Navigating A Web Page
On Sat, Jan 23, 2021 at 02:25 AM, Luke Davis wrote:
So no, I'm afraid the experience is not the same, and the screen reader is not providing the same information.- All accessibility is a workaround, and I have said this on many, many occasions. Substituting sight with audition, which is what screen readers do, will never, ever be an "exact match" for what someone sees, because it can't be. There is no winning here. There have been plenty of complaints (and I'm not saying from you, but you've been around here long enough to see them, multiple times) about a screen reader being "too verbose" and announcing things that a given end user doesn't want or need. You could, I am certain, force a screen reader to announce something like, "Modal dialog," or, "Overlay dialog," when shifts of focus occur to one, which will be loved by some and hated by others. But one thing is for certain, when those occur you, as a screen reader user, should be "trapped" in them by the screen reader in the same manner a sighted user is by sight. If this is not how it's being handled, then that's how it needs to be handled, as in reality you do not have access to the underlying webpage until and unless that modal dialog is dismissed. I can't speak to whether the issue lies with NVDA, the web browser(s), or a combination of both. At this point, I'm not even going to try to retest with Brave. If there is an issue, any issue, with accessibility due to "lack of clarity regarding what's going on" then that needs to be addressed. And, ideally, that happens by someone creating an issue in GitHub (or adding a comment to an already existing one if such exists). I have repeatedly posted on how to create a GitHub account and also posted an MS-Word fillable form that allows those who wish to use it an easier time of filling out an issue ticket, then unprotecting the form, selecting all, and copying and pasting that content in to the issue so that it's impossible to screw up formatting. While this group absolutely can and should serve the purpose of open discussion of issues, and whether those are the result of user error versus software error, when it's the latter it is absolutely no substitute for actually reporting issues to NVAccess. And that's far from impossible (or even all that difficult, really, once you've done it a time or two) for anyone. So if this is a problem, and it appears it is, then those who are having it and can describe what it is that's happening, and what they think should be happening, in light of what has transpired here should go out there and create an issue on GitHub. That's how things get noticed and, possibly, fixed by those in the position to do so. -- Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042 The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself. ~ Brian Vogel
|
|
|
|
Re: loss of shortcut keys
Gene
I don't know if its worth reporting the problem in my case because I use Windows 7. But off and on, the NVDA key stops working. I unload NVDA from the system tray and run it again.
toggle quoted messageShow quoted text
Gene
-----Original Message-----
From: Luke Davis Sent: Saturday, January 23, 2021 2:27 AM To: nvda@nvda.groups.io Subject: Re: [nvda] loss of shortcut keys Don That is the same as the issue I reported here: https://github.com/nvaccess/nvda/issues/11546 To date, nobody else has commented that they are experiencing the same thing. If you could, please go there and leave a comment that you have this issue, including your NVDA and Windows versions. Luke On Fri, 22 Jan 2021, Don H wrote: Running NVDA 2020.4 beta 4 on a Win 10 20h2 system.
|
|
|
|
Re: NVDA and hotkeys in Skype
Kerryn Gunness
toggle quoted messageShow quoted text
you are pressing the correct command
probably try pressing alt, then alt again to regain
focus
then try the command again
|
|
|
|
message announced by NVDA
bering.p
Hi to all.
I am sharing with you an observation I made concerning the announcement of messages by NVDA and which may be the subject of a PR. When the option "Report object descriptions" is disabled, NVDA does not speak the text in dialog boxes. This is annoying when it comes to a message informing the user or questioning him. For example: - following a manual search for update request. - when an add-on uses "gui.messageBox" to query the user. In this case, it is necessary to read the contents of the dialog box using "NVDA + b". I think that any message emitted by NVDA should be announced regardless of the state of activation of the option. What do you think ? And if you agree, please do the PR. best regards. Paul.
|
|
|
|
Re: loss of shortcut keys
Luke Davis
Don
toggle quoted messageShow quoted text
That is the same as the issue I reported here: https://github.com/nvaccess/nvda/issues/11546 To date, nobody else has commented that they are experiencing the same thing. If you could, please go there and leave a comment that you have this issue, including your NVDA and Windows versions. Luke
On Fri, 22 Jan 2021, Don H wrote:
Running NVDA 2020.4 beta 4 on a Win 10 20h2 system.
|
|
|
|
NVDA and hotkeys in Skype
Jarek.Krcmar
Hello all in the nvda group,
I have windows 10 64 bit and skype desktop.
I can’t hang up the talk with the key Ctrl + Shift+ H. If I press the
hotkey, nvda says: “Starting the talk.
For accepting talks mi am using the hotkey Ctrl + Shift + P.
Could you give me an advice, what can I do for hanging talk, please?
Sincerely
Jarek
|
|
|
|
Re: NVDA Screen Review Mode
Gene
When you are in screen review mode, you can move around the
screen and not change your place where you are working, for
example, in a word processor, you can move around and not change
the position of the cursor where you are working. Also, if you
are somewhere where you can't move around using Windows commands
such as up and down arrow, you can look at what is on the screen
in review mode. If an error message ccomes up, you can move
around it using screen review.
Gene
On 1/23/2021 1:14 AM, Blind allday wrote:
|
|
|
|
Re: NVDA Screen Review Mode
Gene
I don't know what you mean by over thinking. Do you know the commands? I can discuss the desktop layout but I don't use or know the laptop layout commands. Have you used the JAWS cursor? Screen review is very similar except that the movement commands are different.
toggle quoted messageShow quoted text
Gene
-----Original Message-----
From: Chris Smart Sent: Saturday, January 23, 2021 12:21 AM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA Screen Review Mode Have you tried the User Guide or the Basic Training module? On 2021-01-22 7:45 p.m., Blind allday wrote: Hello guys, I think I am overthinking NVDA’s Screen Review Mode. Can someone explain it to me? Or point me to where I can learn more about it.
|
|
|
|
Re: Navigating A Web Page
Luke Davis
On Fri, 22 Jan 2021, Brian Vogel wrote:
I have no idea why you say it's an accessibility problem. I just loaded that page with NVDA, and when the dialog appears NVDA begins reading it, and it's controls.In my case, in Brave, I think it started by reading "free unlimited access to radio, playlists and podcasts." At least, the first time I went there. Subsequent tab closings and re-openings, put me wherever I was last on the page, even if it is supposedly covered by that dialog. The latter must be some Brave feature. That's what I'd expect to occur when the overlay occurs, and it does. The screen reader is doing for its user exactly what my eyes do for me.I beg to differ. You have said several times that the dialog is an overlay. Your eyes tell you that the things it's overlaying can not be used until the dialog is acted upon. Our ears do no such thing. Assuming you land on that dialog when the page opens (which is not always the case), there is no indication at all that you are in a dialog. It appears to just be some marketing puffery that is part of the page text. In fact, its headings (there seem to be two of them in the "dialog"), are reachable along with the page's other headings, with H/shift+H. You can demonstrate this by continuing to use the down arrow, or the b key in browse mode, to move "beyond" the supposed dialog, to get to other parts of the page. Your mouse can't access those things (like the play button), from what you've said, but the screen reader can. There is a reasonable presumption: that which can be reached, is meant to be reached. We have no way of knowing that a sighted person can't reach those other parts of the page. So no, I'm afraid the experience is not the same, and the screen reader is not providing the same information. Once the underlying page is obscured by that overlay/modal dialog focus shifts to it and you are forced to interact with it.In neither Firefox nor Brave, was the page ever obscured to NVDA in my tests. In neither browser, was I ever "forced to interact with it". I can easily move up and down, or by element shortcuts, between text in the dialog and things such as music categories, elements of the player, etc. There is no indication whatever that it is a dialog; that it obscures or covers anything; or that it includes a required interaction. This is exactly what it does if you'reWhat you described is nothing like what I experienced in either browser there, so I can only agree with Sascha that it is an accessibility problem. Or, there is an issue with the overlay comprehension in NVDA. In fact I vaguely remember a github issue about overlays not being correctly handled, but I can't now find it. Luke
|
|
|
|
Re: NVDA Screen Review Mode
Blind allday
I have read the user guide but it was a very brief overview of the Screen Review Mode.
On Fri, Jan 22, 2021 at 10:32 PM Chris Smart <ve3rwj@...> wrote:
|
|
|
|
Re: NVDA Screen Review Mode
If you mean ObjectNAV, it's not that scary.
On 2021-01-22 8:56 p.m., Sarah k
Alawami wrote:
|
|
|
|
Re: NVDA Screen Review Mode
Have you tried the User Guide or the Basic Training module?
On 2021-01-22 7:45 p.m., Blind allday
wrote:
|
|
|
|
Community add-ons notice: add-ons to be reviewed by me must be written strictly in Python 3, effective February 1, 2021
Hello all, Because I know that several add-on authors are members of NVDA users list and may or may not be part of NVDA Add-ons list, I’m writing this notice so resident add-on authors can be aware of changes taking place in add-on review process:
Effective February 1, 2021, any add-on authors seeking add-on review from me must write their add-ons in strict Python 3 mode.
Background: January 2020 marked end of life for Python 2. Since then, many projects have switched to Python 3, including NVDA with the release of 2019.3.
As a community add-ons reviewer, I didn’t really care about Python 2 and 3 compatibility for a while, knowing that add-ons may need to be written to support old and new NVDA releases. That window is coming to a close: effective February 1, 2021, any add-on to be reviewed by me must be written strictly in Python 3. This is so that the community can standardize on Python 3 from now on. I will make an exception if authors can demonstrate that parts of their add-on must be compatible with NVDA 2019.2.1 or earlier, and if so, I’ll keep that in mind as I review your add-ons.
Note that this policy deals with add-on reviews to be done by me – other community add-on reviewers may have their own policies about Python 3. But to help the community, I recommend moving to strict Python 3 development environment when writing add-ons.
Thanks. Cheers, Joseph
|
|
|
|
Re: Accessible Video Editor
Debbie April Yuille
What do you mean by gluing the videos together? Can’t you merge them?
Debbie
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sarah k Alawami
Sent: Saturday, 23 January 2021 7:04 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Accessible Video Editor
No, I edit videos in reaper all the time. I can do it as quickly as I can a sound file. Just don't glue the items together, or the video will be black. -- Sarah Alawami, owner of TFFP. . For more info go to our website. Check out my adventures with a shadow machine. to subscribe to the feed click here and you can also follow us on twitter Our discord is where you will know when we go live on twitch. Feel free to give the channel a follow and see what is up there. For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page You will also be able to buy some of my products and eBooks there. Finally, to become a patron and help support the podcast go here On 22 Jan 2021, at 11:37, Christian Ohrens wrote:
|
|
|
|
Re: Navigating A Web Page
On Fri, Jan 22, 2021 at 10:57 PM, Sascha Cowley wrote:
Using Firefox, it was not announced, nor was focus trapped in it.- The behavior in Firefox is quite different than it was in Brave. Eventually this thing was announced, but I was definitely not trapped in it and the screen reader circled back to announcing what was actually on the screen masked by this modal dialog. I would love to know why something this seemingly straightforward is handled so differently by two different web browsers, even two with completely different rendering engines. But you're absolutely correct that what one could logically infer under Firefox (very little) is very, very different than what one could using Brave (and I'd guess other Chromium-based browsers, though I haven't tried). -- Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042 The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself. ~ Brian Vogel
|
|
|
|
Re: Navigating A Web Page
Sascha Cowley
Fair enough. Using Firefox, it was not announced, nor was focus
trapped in it. Perhaps that was just something I did though, or a
bit of a fluke.
On 2021-01-23 11:03, Brian Vogel wrote:
On Fri, Jan 22, 2021 at 06:55 PM, Sascha Cowley wrote:
|
|
|
|
Weather Plus
Andrea Sherry
This addon appears to be functioning badly on my computer i.e. reporting wrong temperatures etc.
Andrea
|
|
|
|
Re: NVDA Screen Review Mode
Actually tha'ts not quite true. I use screen review on a lot of newer programs and activate things with the mouse. I use screen review to read the screen, route and click. I never if I can help it use object review. Take care -- Sarah Alawami, owner of TFFP. . For more info go to our website. Check out my adventures with a shadow machine. to subscribe to the feed click here and you can also follow us on twitter Our discord is where you will know when we go live on twitch. Feel free to give the channel a follow and see what is up there. For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page You will also be able to buy some of my products and eBooks there. Finally, to become a patron and help support the podcast go here
On 22 Jan 2021, at 17:22, Joseph Lee wrote:
|
|
|
|
Re: NVDA Screen Review Mode
Hi, Ah, I see. What you are describing is called “focus mode” where whatever key you press will be dealt not by NVDA but by the web application you are using. For example, pressing K while playing a YouTube video will pause the video if focus mode is on, whereas NVDA will move you to the next link if browse mode is active. Screen review, on the other hand, will let you review the contents of an app’s window. For example, under older programs, activating screen review mode will let you see the contents of the app that aren’t accessible with keyboard commands. These days screen review would not work properly in newer apps but you can find out the contents of a window by doing an OCR (NVDA+R). Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Blind allday
Sent: Friday, January 22, 2021 5:12 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA Screen Review Mode
Well, I thought that screen review mode meant that a page allowed you to activate certain shortcuts that a page had. For example, on YouTube you can press “K” for it to pause and play.
On Fri, Jan 22, 2021 at 4:49 PM Joseph Lee <joseph.lee22590@...> wrote:
|
|
|