WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: navigating applets

for

From: Shane Anderson
Date: Jul 7, 2004 9:53AM

-----Original Message-----
Liza asked:

So what happens when you have a web-based application which MSUT be
accessible - like an Oracle Form running in a browser window (IE6.0) -
how do you cater for accessibility here if its web based ???

Not sure which set of WAI guidelines should it adhere to ?? WCAG or
UAAG ??
Any ideas on the subject ?

My answer:
I am not completely familiar with Oracle Forms but the basic principles still apply. Can the user access the content via the keyboard? Can assistive technologies get at the content?

I have talked to people at Oracle and know that they have worked hard to make their products as accessible as possible.

Now regarding the feedback Oracle sent by sllists:


I asked this question a while back and I got a reply from someone at Oracle..
Conversation below
--------------------

Oracle Forms 6i runtime is accessible while both the builder and runtime is
accessible in Forms 9i.
We have a link to a 'Forms Applications White Paper' at
http://www.oracle.com/accessibility/
The direct link to the white paper is
http://www.oracle.com/accessibility/apps02.html

Any questions about accessibility at Oracle can be sent to
<EMAIL REMOVED>



My comment on this:
I will assume that there is a context here that is not included in this email, because there needs to be some clarificaiton. The claim that &quot;Oracle Forms 6i runtime is accessible&quot; means nothing. Its like saying HTML is accessible. Reading the white papers it is made clear that Oracle forms can be made accessible IF (big IF here) the developer uses the principles set out by Oracle and IF (another big IF) the users computer is properly configured (e.g. the java access bridge must be installed for screen reader users). Technologies like java and flash are not yet robust enough for all users. That does not mean that you don't use the technologies, it means that the user's experience should not be limited to the technologies that are difficult or impossible for them to use. Quoting myself: &quot;They (applets) are effectively used in environments where there exists some control over the users computer (e.g. a company intranet).&quot;

The other oricle feedback email:


Applications developed with forms can certainly meet the standards of
section 508. Rather than 1194.22 which really applies to Web pages and HTML
applications, Forms can be coded to meet 1194.21 - Software Applications and
Operating Systems. Obviously, as you say this involves following the coding
standards white paper. Indeed, much of Oracle Applications is coded in Forms
(albeit version 6i) - for which VPATs are available on the Oracle website.
Please don't hesitate to ask me any questions.



My comment on this:
Here again there needs to be some clarification. It is true that applets do need to meet 1194.21, see 1194.22(m). The ability to access the applet, while not explicitly required, is needed for any &quot;real&quot; accessibility. I am unaware of a method for accessing applets via keyboard surrounded by HTML content. If anyone knows of a way to do it please let everyone know.


Shane Anderson
Programmer Analyst
Web Accessibility in Mind (WebAIM.org)