Test keyboard navigationWhen doing things by voice doesn’t work directly the user can revert to using keyboard commands by voice.Label everything, inc. form elementsFor something to be clickable it must be associated with some text that is pronounceable.Use unambiguous labels that are pronounceable. Do not use lots of identical labels (e.g. click here). Make it clear what the labels are for form elements.Avoid frames or use sparinglyMoving from one frame to another is quite difficult by voice, especially if there are scrollbars within any of the frames.Use standard Windows/HTML controls (buttons and text entry boxes especially)Java applets are notoriously badVisual design often trumps functionality, especially where accessibility is concerned.Ensure cross browser compatibilitySpeech recognition users are often restricted to particular browsers.
Browsers and speech recognition
Using Speech to Browse the Web<br />Kris Roger @KrisEdTech<br />Centre for Learning Technology<br />
Why do I use speech recognition software?<br />
Best practice for speech navigation accessibility<br />Test keyboard navigation<br />Label everything, inc. form elements<br />Avoid frames or use sparingly<br />Use standard Windows/HTML controls <br />Ensure cross browser compatibility<br />
Dragon browser compatibility<br />Dragon NaturallySpeaking 11<br />Works well with:<br />Firefox 3.x<br />Internet Explorer 7/8<br />Works only using gleebox:<br />Google Chrome<br />Safari<br />Does not work at all with:<br />Firefox 4/5<br />Internet Explorer 9<br />
WSR browser compatibility<br />Windows Speech Recognition (Windows 7)<br />Works well with:<br />Internet Explorer 8/9<br />Kind of works with:<br />Firefox 3.x<br />Google Chrome<br />A horrible experience:<br />Firefox 4/5<br />
Essential reading<br />Guidelines For Speech-accessible HTML for Dragon® NaturallySpeaking<br />http://tinyurl.com/speechHTML<br />Guidelines for Developing Windows applications Compatible with Dragon®NaturallySpeaking<br />http://tinyurl.com/speechWinGuide<br />