![]() ![]() And that is the answer to your comment about Section 508… with VoiceOver turned on, Macs are fully Section 508-compliant (and comply with much other non-discrimination legislation around the world). Going further, you can learn all about VoiceOver using the links Baltwo gave you. ![]() To select your chosen item, press Return. It works with drop-down menus too… as soon as you are on one, press Space, and it will open. Although fully sighted, I also use this method, as it does save jumping to a mouse or stretching the thumbs down to a trackpad. This is how some low-vision users manage their Macs, without turning on VoiceOver. Whenever the thing you want to activate is highlighted (with a pale blue outline), press the space bar. ![]() Then you can use the Tab key to highlight the different dialogue buttons in turn, and move around tabs, text fields, etc. You can also toggle this setting using Ctrl-F7. To use this Web Console you will need an updated controller with some JSONP REST API improvements (Juha is going to commit this to the controller trunk but at present a version is available here, if you are using a special branch then merging my REST API changes into the branch you are using should work fine).The simplest answer to your original question is to go to System Preferences -> Keyboard -> Keyboard Shortcuts and at the bottom of the page, click on the All controls radio button. I tend to keep a pre-compiled WAR version of the latest commit here to save you compiling. After a little bit more work I will be pushing WebConsole 2.0 to the community for some alpha testing and you're more than welcome to try this out as it stands right now (committed code is changing quite frequently but I only commit in a usuable state), the branch I am using for development is the one you pointed to above and it will try and load a default controller and panel configuration (if one isn't defined then you will be prompted to enter the Controller URL and a Default Panel Name - unfortunately no Controller Discovery or panel selection at this moment but I will be adding this very shortly):. ![]() This is a complete re-write from the ground up and doesn't share any similarities with the WebConsole 1.0. I have been busy writing WebConsole 2.0 for the past few months and a working alpha version is pretty much there. Which version of the GWT Console should I be working with? Have folks had much success with the GWT console so far? Any hints of things to do for troubleshooting? I have begun to look at the Java code, using Eclipse and Google's GWT Eclipse plugin. Named as Mouseless Browsing v0.5.1, it indexes all your hyperlink links and text boxes in websites that allows users to control the browsing by only tapping on the keyboard buttons. So far, I have not been able to get past the initial screen on either. If you prefer keyboard typing more than mouse browsing, you may interested on this simple Firefox add-on. I've done some legwork, trying out the GWT Console from both and. The Mouseless Browsing add-on ( ) works by modifying the current web page's DOM tree to insert little numbers next to links, text boxes, etc., intercepting numbers typed by the user and causing links to be clicked on, fields selected, etc. I'm looking to combine the GWT Console and the Mouseless Browsing Firefox add-on to enable someone who uses their computer via an eye-scanning device to control the lights in his house. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |