Re: Future of NVDA
Hi Quentin!toggle quoted messageShow quoted text
Let me give you a living example that clarifies what I meant in a better way:
If I am on the desktop using say my Brailliant BI32 regardless of how and what Braille is tethered to the keys are locked to where I am, the display shows only the icon I have highlighted. I am not thinking just when we are on the web I want the Braille display to navigate freely regardless of where we are, I have Microsoft Surface Pro 4 with type cover i.e laptop keyboard layout.
I wish my requests get to the devs via this list, am not expert of this Gethub thing and I don't like the Braille display keys to interrupt speech.
I wish if anybody is against what I take up in Braille let's find a toggle for these things, thanks.
Indeed as Andre has said, there are a number of improvements to Braille coming soon in 2017.3 (the Release candidate is due out in a couple of weeks - the final version a week or so after that unless any big bugs are found). Not addressing all your concerns, but things like input and the web particularly have big advances.
Re accessing all the screen. It depends on what you want, but as a starting point, are you familiar with Object navigation and the review cursor? They let you explore parts of the screen you can't get to with regular navigation keys. By default, the Braille display is tethered to the focus, but NVDA+control+t changes it to be tethered to the review cursor. As Andre mentioned, it's worth exploring the Braille settings, and the associated section in the User Guide as they have many things, some of which may assist with what you are after. Also the section of the User Guide for your particular model or brand.
On Wed, Aug 9, 2017 at 1:37 PM, George Zaynoun <email@example.com <mailto:firstname.lastname@example.org>> wrote:
This is my first message to this list.
What most concerns me now is the Braille support in this free screen reader.
I want the navigation keys on any Braille display to function on the whole screen and not just locked to the current line. If possible make Braille navigation support function like in Dolphin screen reader or Freedom Scientific's JAWS.
Braille input according to selecting a Braille table should be addressed, so say I select Swedish for output there should also be Swedish input same for Arabic, input and output can be separate or combined together with a checkbox.
Likewise changing synthesizer language should in my opinion affect Braille table through a checkbox, however I like using the profile method now.
Espeak sounds horrible in Arabic, would be nice to devote great development work to it, more concerns later.
Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/ <http://www.nvaccess.org/shop/>
Ph +61 7 3149 3306 <tel:%2B61%207%203149%203306>
Timmerv. 6A ITR LGH1102, 54163 SKÖVDE SWEDEN
Tel: +46 (500) 48 29 29 +46 (500) 43 55 11