Hi, Pranav, I am using Office365, but the same is true for Office2019, F6 can return to the body of the document. In addition, when NVDA reports the "Toolbar", a rectangular box is displayed on the sc

#advisory

Hi Rowen, What version of Word are you using? When you get to the toolbar, does pressing f6 cycle you to the document? Otherwise, try the alt key or the escape key. Pranav

#advisory

Hi, Pranav, It is true, not limited to the first two, it may be the first three or more, but there is always a chance to become what I said. When I select "Edit Comment", the normal situation should b

#advisory

Hi Rowen, Are you saying that the approach I mentioned in my message only works for the first 2 comments? Try hitting f6 to return to the document and then repeat the process. Pranav

#advisory

Hi, Pranav, thank you for your reply. I did this before, Editing the first and second comments did not encounter any problems, But they cannot be edited later. NVDA announced the "toolbar".

#advisory

Hi Rowen, You need to use Microsoft Word’s comment navigation feature. Navigate to the review tab in the ribbon and then use the “next comment” and “previous comment” items to navigate to your comment

#advisory

I have a document with a number of comments. When I move to the position containing the comment and press Application to select "Edit Comment", NVDA reports the "Toolbar". At that time, I could not ed

#advisory

Hi, The other side is labels – it isn’t enough to provide keyboard-based navigation for those relying on keyboards; what makes a difference for many is properly labeled controls. Cheers, Joseph

#advisory

Thanks all for your help. So would that mean if it's working fine with keyboard using tab and other shotcuts its fine.

#advisory

I agree, it’s the other side of us requiring Microsoft to be consistent with the handlers they provide for accessibity. We then need to be consistent with the implementation of windows keystrokes we u

#advisory

I'd have thought both have their place in a properly designed system. Standard use of windows keys is surely a must. Brian bglists@... Sent via blueyonder. Please address personal E-mail

#advisory

i believe yes, using arrow and tab keys is the best and most accessible way.

#advisory

For texas submission do we need to have tab key or arrow key compatible for all type of content, do we need to ensure that all content is 100% accessible via tab key or arrow key.

#advisory

It's not broken here. I hear the beeps when text and stuff scrols. Take care

#advisory

There's a hidden config setting to change this. Edit %appdata% vda vda.ini, and in the speech section add: beepSpeechModePitch = 2500 And reload with NVDA+ctrl+r. You can also do this in the Python co

#advisory

Ahh, ok, that did work, loading a large text file into notepad, and scrolling around with the arrows did indeed produce the high pitched beeps. However, when I typed that same text file at the command

#advisory

If I try this, I get some beeps if I issue commands like dir/w. I would imagine just dir would do something as well. the beeps don't sound for long. I tried it with cls and I heard some beeps. Do you

#advisory

Try using it in a list of folders and files or on the desktop and move around. Or move line by line in a document. There will be very high very rapid beeps. Gene

#advisory

I am not sure what the beeps are actually for. Its always been if you push a key it beeps but thats it. There was a speech omitter addon which got rid of beeps mode entirely.

#advisory

In general, when I'm in a command prompt, and I switch on beeps, it doesn't give me any beeps, regardless of what I'm doing. Whether it's a large compile (GNU's modula-2 system is *very* large), or th

#advisory