E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 7 (In chronological order)

From: Sinead Hogan
Date: Thu, Jul 28 2005 3:29PM
Subject: Flash interaction and screenreaders
No previous message | Next message →

Hello,
I'm wondering if text entry into a text field in Flash is possible while using a screen reader. I'm designing some interactive Flash content, and I simply cannot get Jaws to let me enter text. I thought it might be something equivalent to FORM mode, or MSAA off for Window Eyes, but when I try that it says it cannot detect a form. Can someone tell me if this is possible at all, and if so, if it is something I need to design/develop for in Flash or some configuration setting in the screen reader?
Any advice would be much appreciated.
Sinead.

From: Andrew Kirkpatrick
Date: Thu, Jul 28 2005 8:58PM
Subject: RE: Flash interaction and screenreaders
← Previous message | Next message →

I'm wondering if text entry into a text field in Flash is
possible while using a screen reader. I'm designing some interactive
Flash content, and I simply cannot get Jaws to let me enter text. I
thought it might be something equivalent to FORM mode, or MSAA off for
Window Eyes, but when I try that it says it cannot detect a form. Can
someone tell me if this is possible at all, and if so, if it is
something I need to design/develop for in Flash or some configuration
setting in the screen reader?

You will need to use forms mode/MSAA off in order to enter text,
but it should work without a problem. If you start at the top with JAWS
and use the arrow keys to read through the content, does it ever say
"edit"? If not, then you may have disabled access to the Flash movie
inadvertantly. Can you provide more information?

Thanks,
Andrew
Andrew Kirkpatrick
Principal Accessibility Engineer, Macromedia
= EMAIL ADDRESS REMOVED =

From: Sinead Hogan
Date: Fri, Jul 29 2005 12:07PM
Subject: RE: Flash interaction and screenreaders
← Previous message | Next message →

Thank you for that Andrew. I have managed to enter text with Window Eyes now by turning MSAA off. This experience has made me wonder though: What about shortcut keys? As far as I can tell, both Jaws and Window-eyes have reserved many/most(!) keys for screen reader operation. So I'm wondering what is best practice is for assigning keyboard shortcuts/alternatives to commonly used commands/buttons for keyboard dependent users. Is there a reserved set of keys that no screen reader will react to, or do you need to turn off/pause the screen reader in order to user another application's keyboard alternatives??
Thanks again,
Sinead.

From: Glenda Watson Hyatt
Date: Fri, Jul 29 2005 12:27PM
Subject: RE: Flash interaction and screenreaders
← Previous message | Next message →

Sinead,

I know you mean well by wanting to include accesskeys [I'm assuming that is what you are referring to], but, even though a great concept, accesskeys have serious flaws when implemented. One such flaw is the limited number of keyboard combinations not assigned to other programs [browsers, assistive technology]. There are other flaws too, which I'm sure John will enthusiastically elaborate on.

Accesskeys seems to be one of those accessibility features that needs to go back to the drawing board.

HTH,
Glenda

Glenda Watson Hyatt, Principal
Soaring Eagle Communications
Accessible websites. Accessible content. Accessible solutions.
www.webaccessibility.biz

From: Andrew Kirkpatrick
Date: Fri, Jul 29 2005 1:20PM
Subject: RE: Flash interaction and screenreaders
← Previous message | Next message →

Thank you for that Andrew. I have managed to enter text with Window Eyes
now by turning MSAA off. This experience has made me wonder though:
What about shortcut keys? As far as I can tell, both Jaws and
Window-eyes have reserved many/most(!) keys for screen reader operation.
So I'm wondering what is best practice is for assigning keyboard
shortcuts/alternatives to commonly used commands/buttons for keyboard
dependent users. Is there a reserved set of keys that no screen reader
will react to, or do you need to turn off/pause the screen reader in
order to user another application's keyboard alternatives??

This is a problem for all application development, including Flash. In
JAWS you can disable navigation quick keys by pressing ins+n, so if you
are using lots of keys you may need to communicate to users how to do
this. There is no reserved set, and there is no guarantee that a key
that is available today won't be used in a screen reader tomorrow. Wish
I had better news for you...

AWK
Andrew Kirkpatrick
Principal Accessibility Engineer, Macromedia
= EMAIL ADDRESS REMOVED =

From: Sinead Hogan
Date: Fri, Jul 29 2005 3:28PM
Subject: RE: Flash interaction and screenreaders
← Previous message | Next message →

Hi again,
Yes, I was referring to access keys (sorry, i'm a newbie!)
This brings me to wondering if its possible to make some interactions accessible at all to users of screen readers who can only use a keyboard. For example I could (hopefully!) make my menu system and other interactions accessible to keyboard-only users, and I could make them readable to screen readers. But does this issue of access key use by screen readers mean that it isn't possible to make some interactions accessible to both at once?
Bit of background: I'm involved in building highly interactive elearning-type software in Flash. It simulates the windows desktop environment and involves allowing users carry out almost the full range of mouse and keyboard interaction types. It will be delivered in a web browser.
From what I understand so far though, I would have this same issue if I was using technologies other than Flash. Right?
Forgive my ignorance if I'm way off, but I'm feeling dizzy at what seems like an overwhelming task!
Sinead.

From: Andrew Kirkpatrick
Date: Mon, Aug 01 2005 9:21AM
Subject: RE: Flash interaction and screenreaders
← Previous message | No next message

Yes, I was referring to access keys (sorry, i'm a newbie!)

I'm not entirely clear that you are. If the keyboard shortcuts are in
the Flash content, then you're not, but you will have many of the same
problems and frustrations that come with the use of the accesskey
attribute in HTML..

This brings me to wondering if its possible to make some interactions
accessible at all to users of screen readers who can only use a
keyboard. For example I could (hopefully!) make my menu system and other
interactions accessible to keyboard-only users, and I could make them
readable to screen readers. But does this issue of access key use by
screen readers mean that it isn't possible to make some interactions
accessible to both at once?

No, it doesn't mean that. It is preferable to have one version instead
of separate versions.

Bit of background: I'm involved in building highly interactive
elearning-type software in Flash. It simulates the windows desktop
environment and involves allowing users carry out almost the full range
of mouse and keyboard interaction types. It will be delivered in a web
browser.
>From what I understand so far though, I would have this same issue if I
was using technologies other than Flash. Right?

Yes, you would.
AWK
Andrew Kirkpatrick
Principal Accessibility Engineer, Macromedia
= EMAIL ADDRESS REMOVED =