[Accessibility] FSG102 Document Part 1 Section C working copy

Doug Beattie dbb at linkexplorer.com
Wed Jul 2 15:54:52 PDT 2003


Attached is the "C" section of Part 1 of our FSG102 document.
Please work on revising it through this mail list so we can
get it to a point we feel comfortable with ASAP.

Thanks,
Janina and Doug

-------------- next part --------------
1. IDENTIFY PROBLEM AND PROPOSED SOLUTION ABSTRACT

(FSG102-1) is an initial declaration of the problem and an abstract of
the proposed solution. This document should be revised throughout the
formation of the Workgroup to reflect any changes and will act as the
basic justification of further work. It should include the following:

...
	
 c. Existing software, partial solutions, etc.  Implementations of the
    proposed standard should already exist (usually produces a less
    buggy standard), or should exist in approximate form (for example,
    no Unix complied with the first POSIX standard at the time it was
    being written, but many were close), or there should be an
    indication of what new implementation work will be needed.

We benefit from the fact that the greater majority of the requirements
have been previously implemented, sometimes on several platforms, though
usually on proprietary ones. The value and viability of such standards
is, therefore, well established. The most comprehensive solutions
available today were created for Microsoft Windows computers. An
incomplete solution has long been available on Macintosh computers.
Elements exist for free and open platform desktops, and significant
robust solutions for certain user communities are well established on
the console side of free and open platforms. Examples include:


keyboard accessibility:

         end-user features:
                  AccessX,
                  Gnome's Keyboard Accessibility Preferences Dialog
         APIs/ABIs:
                  XKB Specification, X.org


Accessibility APIs/ABIs: (i.e. existing open solutions and also prior
art
                         in the proprietary domain):

         applications-side:
                        ATK
                        Java Accessibility API
                        UNO Accessibility API
(StarOffice/OpenOffice.org)

         assistive-tech client-side:
                        Java Accessibility API
                        Mac Accessibility API
                        GNOME's Assistive Technology Service Provider
Interface
  (AT-SPI)
                        Microsoft Active Accessibility (MSAA)


Accessibility-related utilities:

          gnome-speech text-to-speech APIs
          gnome-mag magnification APIs




More information about the Accessibility mailing list