RE: [flexcoders] Re: Flex buttons and screen readers
We're working on Flex 3 support now, and should have that available very soon after Flex 3 ships, if not simultaneously. I have received some reports of install problems. My install works fine, so I know it's working for some. I'm hoping to have a fix for this next week. - m -Original Message- From: Nathan Dickamore [EMAIL PROTECTED] Sent: Friday, February 08, 2008 7:04 PM To: flexcoders@yahoogroups.com flexcoders@yahoogroups.com Subject: [flexcoders] Re: Flex buttons and screen readers Matt, The link that you posted states support for JAWS 6.1 and 7.0 Not 6.0 and up. I tried using the scripts for JAWS 9.0 but it does not work. The error message asks about the validity of the install. Has anybody had any better luck or does anyone know if there is going to be support for JAWS 9.0 or even support for Flex 3? Nathan --- In flexcoders@yahoogroups.com, Matt Morgan-May [EMAIL PROTECTED] wrote: I wouldn¹t recommend testing with Narrator. I¹ve never encountered a single Narrator user. We do the bulk of our testing on JAWS and Window-Eyes. In the US, JAWS has the majority share of the screen reader market, and we support Flex 2 on JAWS 6 and up. If you¹re testing with JAWS, you will need to install the JAWS scripts for Flex: http://www.adobe.com/macromedia/accessibility/features/flex/jaws.html Hope this helps. m On 2/1/08 2:24 AM, moogster31 [EMAIL PROTECTED] wrote: 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 jason.merrill@ 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 GTO LLD 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
RE: [flexcoders] Re: Flex buttons and screen readers
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 GTO LLD 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 GTO LLD 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
Re: [flexcoders] Re: Flex buttons and screen readers
I wouldn¹t recommend testing with Narrator. I¹ve never encountered a single Narrator user. We do the bulk of our testing on JAWS and Window-Eyes. In the US, JAWS has the majority share of the screen reader market, and we support Flex 2 on JAWS 6 and up. If you¹re testing with JAWS, you will need to install the JAWS scripts for Flex: http://www.adobe.com/macromedia/accessibility/features/flex/jaws.html Hope this helps. m On 2/1/08 2:24 AM, moogster31 [EMAIL PROTECTED] wrote: 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 GTO LLD 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
