<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Musings of a Trained Monkey: Tag accessibility</title>
    <link>http://www.stevelongdo.com/articles/tag/accessibility</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Accessibility of Applets versus Flex RIAs...</title>
      <description>&lt;p&gt;I&amp;#8217;ve been doing some research into providing support for &lt;a href="http://www.section508.gov/index.cfm?FuseAction=Content&amp;#38;ID=12"&gt;section 508 accessibility compliance&lt;/a&gt; for a simple file browser available inside a web browser.  There really is a dearth of information available on the topic from a software implementation stand point. 
&lt;br /&gt;&lt;br /&gt;
&lt;strong&gt;Java&lt;/strong&gt; Applets seem to pay lip service to providing support for accessibility by the addition of tons of code labels that would need to be maintained with each release.  Certain activities don&amp;#8217;t seem to be supported at all for users with accessibility needs (&lt;em&gt;opening tree nodes for example&lt;/em&gt;).  The most recent documentation I could find on Applets and Accessibility on Sun&amp;#8217;s website is called &lt;a href="http://java.sun.com/developer/technicalArticles/GUI/accessibility2/"&gt;What&amp;#8217;s new in Accessibility and is dated &lt;strong&gt;October 30, 2000&lt;/strong&gt;&lt;/a&gt; clearly Sun took their role as an industry leader in web technology very seriously&amp;#8230;back in &lt;strong&gt;2000&lt;/strong&gt;. (As an aside is referring to a user of an applet as a &lt;em&gt;&lt;strong&gt;Robot&lt;/strong&gt;&lt;/em&gt; just a little offensive to anyone besides me?)
&lt;br /&gt;&lt;br /&gt;
&lt;a href="http://www.adobe.com/products/flex/"&gt;Adobe Flex&lt;/a&gt;, however, seems to view accessibility as a core issue in the design of their product.  So much so that they provide a very simple xml attribute for &lt;span class="caps"&gt;MXML&lt;/span&gt; files (&amp;lt;accessibility&amp;gt;true&amp;lt;/accessibility&amp;gt;) to turn on a host of accessibility features.  This requires almost no extra effort on the part of a software developer.  There are a small number of caveats to their support, but they have taken the &lt;a href="http://www.adobe.com/macromedia/accessibility/features/flex/best_practices.html"&gt;steps to detail them and best practices for accessibility&lt;/a&gt; on their site including a functional understanding of how Flex works with &lt;strong&gt;&lt;span class="caps"&gt;JAWS&lt;/span&gt;&lt;/strong&gt; and &lt;strong&gt;Braille screen&lt;/strong&gt; technologies.  Adobe even maintains a &lt;strong&gt;current&lt;/strong&gt; &lt;a href="http://www.adobe.com/accessibility/"&gt;website dedicated to the accessibility of their products&lt;/a&gt;.
&lt;br /&gt;&lt;/p&gt;</description>
      <pubDate>Sat, 26 May 2007 18:58:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:0e54f352-329a-4f0e-8589-664471c67a24</guid>
      <author>Steve Longdo</author>
      <link>http://www.stevelongdo.com/articles/2007/05/26/accessibility-of-applets-versus-flex-rias</link>
      <category>flex</category>
      <category>adobe</category>
      <category>java</category>
      <category>accessibility</category>
    </item>
  </channel>
</rss>
