Please report your screen reader, browser, and Windows versions. Did you try turning off the virtual cursor and repeatedly tabbing? You should reach fruit basket controls if the Silverlight 4 runtime is available. Otherwise, there should be a link to install the latest Silverlight.
Jamal On 5/27/2011 3:56 PM, Katherine Moss wrote:
I tried your Silverlight app, and I could only get the page to open. I could see nothing on the page at all. -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui Sent: Thursday, May 26, 2011 5:23 AM To: blindwebbers@xxxxxxxxxxxxxxx; programmingblind; Program-l Subject: Comparing fruit baskets in Flash, Silverlight, and native HTML I have revised the Flex/Flash fruit basket program I previously did so that the code is simpler, taking advantage of default accessibility behavior in the Spark components of the Flex 4 framework. The code is in the file FruitBasket.mxml within the archive http://EmpowermentZone.com/flex_fruit.zip I also resolved Firefox compatibility issues, and added auto-detection of Flash Player, with JavaScript to upgrade or install the latest Flash Player runtime if not found. The Flex fruit basket app may be tried at http://EmpowermentZone.com/flex_fruit.htm Similarly, source code and a build batch file using command-line tools is available for a Silverlight 4 fruit basket at http://EmpowermentZone.com/sl_fruit.zip and the app may be tried in a browser at http://EmpowermentZone.com/sl_fruit.htm A few years ago, I did a fruit basket in native HTML 4 and JavaScript, which may be tried at http://EmpowermentZone.com/js_fruit.htm These are three different approaches to building rich Internet applications (RIAs). Not surprisingly, if functionality can be achieved with native HTML controls, it tends to be more accessible with screen readers. When functionality requires custom JavaScript controls (AJAX widgets), however, or controls from the Flash or Silver light plug-in, it is less clear which approach will maximize accessibility and usability. I hope that these samples help one compare approaches from either a developer or user standpoint. I tested on Vista32 with JAWS 10 and above, the latest NVDA, and Window-Eyes 7.5, using either Internet Explorer 8 or Firefox 3.6. I found that all three screen readers worked with each RIA approach in either web browser. JAWS and NVDA did not recognize the Silverlight controls in virtual browse mode (a forms or application mode needed to be toggled on). Those screen readers did recognize the Flash controls, but JAWS required a refresh of its off screen model (Insert+Escape) in order to do so. Window-Eyes, on the other hand, recognized both the Flash and Silverlight controls in virtual browse mode and without a screen refresh. Others may experience different results, and you are invited to share your comparisons. Please be specific about operating system, screen reader, and web browser versions if yu do. Of course, other issues may arise with a more complex app. It is my understanding that neither Orca on Linux nor VoiceOver on the Mac currently support either Flash or Silverlight controls. Jamal __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind
__________View the list's information and change your settings at //www.freelists.org/list/programmingblind