Browse Prior Art Database

Enhanced Assistive Screen Reading Tool Disclosure Number: IPCOM000010311D
Original Publication Date: 2002-Nov-20
Included in the Prior Art Database: 2002-Nov-20
Document File: 1 page(s) / 38K

Publishing Venue



Enhanced Assistive Screen Reading Tool

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

Page 1 of 1

Enhanced Assistive Screen Reading Tool

There are currently many inadequacies with assisting technology tools, such as screen readers. One area this is very evident is in the Java platform. Currently, there are no OS native screen readers that support Java. Instead, they rely on the Java Accessibility Bridge to translate the Java components to where the OS native screen readers can interpret them. Both the native OS screen readers and the Java Accessibility Bridge support a subset of components, so the final component support is very slim. Also, developers are required to set accessible properties in order to ensure their applications are Section 508 accessible certified. This is required for work with Government software contracts.

The problem is further aggravated by the fact that a screen reader needs to either have focus on an item, or have a "labeledby/lablefor" attribute set for non-focusable items such as panels or dialog text. If that is not possible, the text would actually need to be focusable or documented (as per the Austin accessibility center).

One workaround would be a service that runs in the background, in addition to the current screen reader or as an enhancement to a current screen reader. At a predetermined key sequence (numlock, numlock), the service would then take the current window and break it down into all components. These components would be added sequentially to a vector that could then be "visually traversed" by the disabled user, muc...