WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Dragon Naturally Speaking - "Click Close"

for

From: Kim Patch
Date: Jan 4, 2010 12:45PM

Also take a look at Utter Command, which lets you
- place and click the mouse using a single speech command
- name one or two mouse clicks in a row, which enables otherwise
inaccessible buttons and drop-down menus
- speak the Firefox mouseless browsing extensions -- you can say up to
two numbers in a row

Here's a video that includes the naming-a-mouse-click ability:
http://www.redstartsystems.com/videos.html#unprecedented

In general, it enables all applications and lets you speak in command
phrases.

Caveat -- I'm with Redstart Systems, which makes Utter Command.
Kim Patch

Moore,Michael (DARS) wrote:
> An extension for Dragon that seems to improve the accuracy of Dragon when working with most applications is called KnowBrainer. We have had pretty good success using it.
>
> Mike Moore
> (512) 424-4159
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of <EMAIL REMOVED>
> Sent: Monday, January 04, 2010 8:10 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Dragon Naturally Speaking - "Click Close"
>
> On Mon, 4 Jan 2010, Tim Harshbarger wrote:
>
>> Interestingly, my colleagues, who work with DNS, are uncertain what happens if there only appears to be one button in the window. Typically, if there appears to be one button, they just say the button's name, like "click Close." In fact, they have closed browser windows unintentionally a few times by saying "click Close."
>>
>
> as a DNS user, I usually make use of third-party tools (such as
> the Firefox Mouseless Browsing extension) to provide this
> functionality. Frankly,NaturallySpeaking + existing browser
> technologies aren't yet adequate to make this reliable, not just
> because of the "click close" behavior you are discussing, but
> because the odds of Dragon NaturallySpeaking mishearing the name
> of the button are just too high.
>
> I would lay bets that not one of the developers here, each of
> whom cares very much about designing accessible webpages, worries
> about making link and button names that aren't near homophones of
> each other. (Nor should you all, except in as much if things need
> to be comprehensible to screen reader users.) It's more reliable
> just to stick a unique number next to every clickable item (which
> is what Mouseless Browsing does) than to rely on NaturallySpeaking
> correctly identifying the name of the button clicked.
>
> -Deborah
>