Re: Oracle Meeting - community requests?

  • From: Peter Quaiattini <Peter_Quaiattini@xxxxxx>
  • To: "programmingblind@xxxxxxxxxxxxx" <programmingblind@xxxxxxxxxxxxx>
  • Date: Tue, 18 Jan 2011 18:13:38 +0000

Not that you need to hear another 'me too', however, I, for one wholly agree 
with Jamal's comments.
Ever since Oracle changed away from Metalink to a JAVA-based presentation, 
access to support pages has been very, very painful.   

Peter Quaiattini | Information Technology, OPS - Data Hosting Services | 
peter_quaiattini@xxxxxx | (403) 319-6579 
Canadian Pacific Driving the Digital Railway
-----Original Message-----
Date: Mon, 17 Jan 2011 12:02:13 -0500
From: Jamal Mazrui <empower@xxxxxxxxx>
Subject: Re: Oracle Meeting - community requests?

My suggestions to convey to Oracle are as follows:

* Update the Java Access Bridge so that it implements a more complete 
and modern accessibility API on Windows, such as IAccessible2 and/or 
UIA, and supports 64-bit as well as 32-bit Windows out of the box.

* Implement a strong accessibility API in all non-Java-based GUI 
applications, including Oracle database management products.

* Ensure that all web pages on,, and other company 
sites are compliant with the Web Content Accessibility Guidelines 2.0 
(AA conformance level), as published by the World Wide Web Consortium,

* Renew the company accessibility team that was largely dismantled. 
Developer support of the Orca screen reader was a key contribution by 
Sun to the accessibility field.  Completely voluntary efforts cannot 
replace that support, so the future Viability of Orca under the 
uppcoming Gnone 3 is in jeopardy unless circumstances change 
significantly.  I believe that Orca has the corporate strength to 
support such an accessibility team, which will also aid the compliance 
of its products with Section 508 procurement requirements of the U.S. 
federal government.

View the list's information and change your settings at

Other related posts: