« Sounds on Load and screen readers | Main | Controlling Reading Order OffStage »

July 29, 2003

Screen reader detection

Well, no need for long sorry ass excuses for being offline for so long. Blogs are like that. I blog best when I am at my desk for a couple of days at a time. Not much of that right now. The good news is I am home for a while. Should make things easier.

Today I want to talk about screen reader detection. This is a really unique feature of Flash. Using MSAA, we can look to see if there is a screen reader running and actively looking at the Flash content.

I really do not talk about this feature much, mostly because it makes me nervous. There is a tremendous temptation for designers to develop a "super-cool" inaccessible site and then use detection to point screen reader users to lame text only pages. This is not how to use this features. I strong recommend just using one site and making it as accessible as possible to all users.

In the example below, the Flash movie detects the screen reader using the method, Accessibility.isActive().

Source

There are two things to keep in mind as you are using Flash to detect a screen reader. First, the method may return a false negative if called too early (let's call it a feature, not a bug). Next, the screen reader needs to be focused on the Flash movie at the time of detection. In the example above, I have this by tying the detection to a button. This could be a preloader or another simple button to launch the main content.

Posted by Bob Regan at July 29, 2003 12:29 AM

Comments

That sounds like a cool feature. What happens if the user is using a speech browser that does not support MSAA. The only browser I know that does it at the moment is Window-Eyes. Can you point me to other speech browsers that support this?

Posted by: Sandy Clark at July 29, 2003 12:26 PM

Hi Sandy,

Actually screen readers (speech browsers) must support MSAA in order to support Flash. It is the only means the Flash Player uses to pass data to the screen readers.

The current list includes Window Eyes 4.2+ and JAWS 4.5+.

Posted by: Bob Regan at July 29, 2003 12:29 PM

> I strong recommend just using
> one site and making it as accessible as > possible to all users.

Why?

Ciao,

Rene =>=

Posted by: Rene Liethof at July 30, 2003 10:17 AM

Hi Rene,

In my experience, secondary, 'accessible' sites often become lackluster sites that don't have all of the features of the full site and are not as well maintained. Frequently this is not the intent, but it is how it plays out in practice, almost without fail.

Cheers,
Bob

Posted by: Bob Regan at July 30, 2003 10:24 AM

Bob:
Long time fan, first time blogger.
I recently found this thread and the sample detector- I'm running Windows Eyes 4.5 Beta Demo, and it's not getting picked up by the sample, and there is no button action on tke check button.

That aside, I'm having a nasty time with Windows Eyes right now: I'm working on a CD ROM app, and can get the first page to read correctly, but when the user selects a button, > I get a "CUSTOM CONTROL_ MSAA OFF" announcement from the reader and low and behold, MSAA is set to off. is this a common error, and if so, is there a way to repeatedly check to make sure that both MSAA and Flash access are running n Windows Eyes and JAWS using actionscript, perhaps as an onEnterFrame command? Knowing that a knowledgable user can turn it back on with a ALT SHFT M in windows Eyes, and knowing that not all users are knowledgeable and some of those are using JAWS, I'd like to be able to check the state of MSAA for the User, and turn it on should it be set to off; similarly the Flash feature within both Windows Eyes and Jaws. I don't want to simply toggle it, as it may already be on, and I'd be shutting it off.

Thanks,
Bob Babcock

Posted by: Bob Babcock at August 12, 2003 03:17 PM

Hi Bob (everybody drink),

So I have to admit, I have not played with the beta too much yet. On my to do list later this month as I clear my calendar.

The MSAA mode is comparable to forms mode in JAWS. Window Eyes slips in and out of MSAA mode as the user navigates through a Flash movie. It is triggered by user interactivity much the same way it does in a form. A Flash movie forces the user to use the down arrow to navigate the content after activating a control. Once they do, MSAA mode turns off by default.

That being said, let me get a more sophisticated response from my friends at GW Micro and NCAM.

Thanks for the note!

Cheers,
Bob

Posted by: Bob Regan at August 12, 2003 10:54 PM

Thanks Bob.
Rergards, Bob Babcock

Posted by: Bob Babcock at August 14, 2003 09:10 AM

HI Bob: (Drink again)
Since MSAA shuts itself off, is there a way to call it from action script to turn it on (Accessibility.MSAA.isOn or the such?)

Bob

Posted by: Bob Babcock at August 14, 2003 03:24 PM

Hi Bob

Nope. Designers can't control the screen reader like that (for some very good reasons).

Cheers,
Bob

Posted by: Bob Regan at August 15, 2003 09:14 AM

Hi Bob (Still drinking)
...so what does a developer do to keep a flash presentation accessible from end-to-end?
Regards,
Bob

Posted by: Bob Babcock at August 19, 2003 01:03 PM

Hi Bob,

Well aside from all of the drinkin' (keep in mind I live in WI), a lot of testing.

While HTML designers don't think twice about popping open their pages in multiple browsers, Flash designers tend to stay in the Flash application itself to test their movie.

It is really important with Flash accessibility that you test early and often. Open the flash movie in a screen reader as often as you can when you are in the early design stages to ensure you have not gone down an incorrect path.

Hope that helps.

Cheers,
Bob

Posted by: Bob Regan at August 19, 2003 08:27 PM

Bob (drinking? The lights weren't the only thing blacked out in NYC this weekend):
CTRL+F12 & "Test and Save often"- is that the best you can do for me bobby boy?
Put on the ol' Senior Project Manager hat, or the 'i've written the only book on the subject" hat for a second-
If MSAA goes off with the user's first navigation selection within a flash app when using the latest beta from GW Micro, is Flash to be considered "accessible", or only "initially accessible"? Is there a way to stay within the context of MSAA once someone makes a selection (BTW- no down arrow only tabbing and a return to select- I'd show you the content, but then I'd have to kill you).

Regards, Bob

Posted by: Bob Babcock at August 20, 2003 03:00 PM

I'm looking around your blog, and I'm trying to learn more about MSAA and not finding much. Is there a post that does the intro bit about this? It sounds like a key thing to know when creating an accessible site.

Posted by: Day Kirby at September 2, 2003 11:41 AM

Re: Creating one accessible site.

Rene, from my experience, when users see one version of the site that is in Flash (or some other plugin technolog) and one that is not, there is a sense that the non-Flash version is not only less immersive, but has less content, fewer features, older updates, etc. That is, that the non-flash version is non-interesting.

However, one thing to keep in mind is that if you are doing a non-flash equivalent, that the translation be worthwhile. For instance, instead of just the text transcript for a movie, a text version should capture the spirit and meaning of the non-text content.

A strategy I'm working with on a project right now is to have the non-flash version contain narrative features that the flash version doesn't have. That is, both versions are more interesting than the other, but in different ways.

Not only does that keep people from feeling like 2nd class citizens if they have disabilities, but it encourages people to try both the non-flash and flash versions, especially since we're going through all sorts of efforst to make the flash version accessible.

Accessibliity isn't just about being technically compatible. Note that this idea is built right in to the emerging level 2 WAC standards.

Posted by: Day Kirby at September 2, 2003 11:51 AM

Hi.

Actually, it is not really. I say that only in so much as MSAA shapes a lot of what flash can and can not do but as a designer you will likely never interact with it directly. The only resource on MSAA resides on the Microsoft site. It is a steep learning curve, so be warned!

Cheers,
Bob

Posted by: Bob Regan at September 3, 2003 09:20 AM

Bob:
Do you know of a California based company that does accessibility testing for media?
Bob Babcock

Posted by: Bob Babcock at October 22, 2003 03:15 PM

I understand that Flash player 7 has a screen reader. Does this mean that JAWS or Window-Eyes are not needed for Flash to be accessed by visually disabled folks?

Posted by: Biff LeVee at July 30, 2004 01:18 PM

No, it does not. Flash Player 7 does not have a screen reader, it works with screen readers.

Posted by: Bob Regan at August 3, 2004 02:15 PM