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@blueyonder.co.uk 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

Travic, What are you reading? Can you give me steps to reproduce, please?

#advisory

I'm not talking about the speech beeps add-on either. If you use the nvda-S key to switch to beeps mode, I get no sound at all, that means, no beeps, no speech, no nothing at all when text is scrollin

#advisory

That was basically my point - if we were writing it from scratch now, I'd recommend going the other way, but the effort to change it, when the end result will be essentially the same options for funct

#advisory

I don't see the point of changing it. Is it really that much trouble to use NVDA command twice to get back to speech when it is off? I think working on an add-on and removing beeps is micromanagement

#advisory

I agree. That being said "Beeps Speech Mode" is disjoint from the use of beep tones to report the status of a progress bar. I'm actually hoping that the confusion is now resolved, as the difference be

#advisory

Brian, I agree. In theory it makes more sense to have the core provide the minimum functionality, and for something that only a group of users want, make that available via an add-on. In this case, gi

#advisory

I maybe didn't make it clear enough! sorry my bad! I am not talking about the speech beeps addon I was talking about the beeps that ere built in to Nvda.

#advisory