SWT.... J. -----Original Message----- From: program-java-bounce@xxxxxxxxxxxxx [mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Stanzel, Susan - Kansas City, MO Sent: October 12, 2010 11:48 To: program-java@xxxxxxxxxxxxx Subject: [program-java] Oricle and the Java Access Bridge There is a thread on the other list programmingblind which is talking about Orical dropping support of the Java Access Bridge. Have any of you been following it? As most of you know I am learning Java and work for the United States Department of Agriculture. Here we write our own web applications using Struts. We do not use Java Swing or AWT. Part of the thread has been that the large organizations need to do something about this. As a very long time member of the National Federation of the Blind, since 1974, I am certainly glad to work on this. First I need to understand the issue well enough to explain it. I do know Jim Home has been following this issue. Here is what Steve said: I don't think that Section 508 does anything to influence Oracle's treatment of Sun's product line, including Java and the Java Access Bridge. The Bridge is a tool used to make java applications more accessible. Oracle isn't selling Java applications. As for the things that Oracle DOES sell, I still don't think it will influence them. If the Government buys some EIT, it must be accessible. So says Section 508. Unfortunately, I see this regularly ignored, or simply addressed with a nod and a wink. What I mean by that, is that just because a company provides a VPAT, it doesn't mean it meets the requirements of Section 508. And, even if it meets the requirements, it may still be inaccessible for practical usage by somebody with disabilities. The theory behind Section 508 was that since the government is such a big consumer of EIT, that EIT providers would choose to provide only accessible products, rather than separate versions just for government. Steve Meacham