Browse Prior Art Database

File Monitoring Accessibility Tool Disclosure Number: IPCOM000010312D
Original Publication Date: 2002-Nov-20
Included in the Prior Art Database: 2002-Nov-20
Document File: 1 page(s) / 56K

Publishing Venue



File Monitoring Accessibility Tool

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 96% of the total text.

Page 1 of 1

File Monitoring Accessibility Tool

     Currently there is no consistent screen reader support in
the industry. Even though Section 508 compliance is required for
government software contracts, accessibility tools are an
emerging technology (especially in the area of Java). Currently a
Java developer relies on the Java Accessibility Bridge, which
supports a subset of the native Java objects, which is then
utilized by a OS native screen reader, (like JAWS) which supports
a subset of the Java accessibility bridge.

     Because of these inadequacies, many applications rely on
logging to gain Section 508 compliance. Every dialog needs to
either have the label section a focusable item (breaking IBM UI
guidelines) or log said message. Logging every message.

     Logging the message allows the disabled user the option of
technically getting to the message, and relieves the developer of
Section 508 compliance, but this does not solve the problem that
the user cannot use the message at the time when it is needed.

     A proposal would be an additional monitoring service that
will alert the disabled user when a message is logged to a file,
and read it to the user if so desired. This service could run in
addition to an existing screen reader, or as a supplemental
separate program. This way the disabled user is able to "hear"
the log message entries without having to constantly re-open the
log file and also is able to be alerted when something that the
user cannot read (such as a dialog) is pre...