>>I have spoken to our QA here and they are going to try to get a copy
>>of JAWS to test with.
Freedown Scientific provides a trial version for free - you can download
and test with that.
Jason Merrill
Bank of America
GT&O L&LD Solutions Design & Development
eTools & Multimedia
Bank of America Flash Platform Developer Community
________________________________
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of moogster31
Sent: Friday, February 01, 2008 5:25 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Flex buttons and screen readers
The screen readers that have been run over the site are
WindowsEyes
and Narrator - both of which have encountered some problems with
reading all elements on the screen.
I have spoken to our QA here and they are going to try to get a
copy
of JAWS to test with.
thanks
--- In flexcoders@yahoogroups.com
<mailto:flexcoders%40yahoogroups.com> , "Merrill, Jason"
<[EMAIL PROTECTED]> wrote:
>
> Tabindex has nothing to do with the screen reader - tab index
refers to
> the tabbing between objects with your keyboard (an
acessibility issue
> for sure). The mask could be throwing it off, not sure what
> Screenreader software you are using. I know in the Flash IDE
it helps
> to use dynamic text fields instead of static ones.
>
> We just had a big discussion on the Flash_Tiger list on Yahoo
about Jaws
> screenreader and Flash - search for "Flash and JAWS".
>
>
> Jason Merrill
> Bank of America
> GT&O L&LD Solutions Design & Development
> eTools & Multimedia
>
> Bank of America Flash Platform Developer Community
>
>
>
>
>
>
> ________________________________
>
> From: flexcoders@yahoogroups.com
<mailto:flexcoders%40yahoogroups.com>
> [mailto:flexcoders@yahoogroups.com
<mailto:flexcoders%40yahoogroups.com> ] On Behalf Of moogster31
> Sent: Thursday, January 31, 2008 1:34 PM
> To: flexcoders@yahoogroups.com
<mailto:flexcoders%40yahoogroups.com>
> Subject: [flexcoders] Flex buttons and screen readers
>
>
>
> Hi
>
> I have built an application with buttons behind a mask. The
> buttons
> have all the usual accessibility tags on them (name,
tabEnabled,
> tabIndex) but the screen reader is not reading them out.
>
> The only difference between these buttons and other buttons in
> the
> application is that these are behind a mask.
>
> Has any one come across this before and if so - how did you
> solve it?
>
> thanks
>
> kt
>
