[Accessibility] suggestions on FS102 b

[John Goldthwaite]

Simplify the first paragraph a bit:

Since persons with disabilities generally seek to perform the
same tasks as all other users of technology, it is prudent,
expedient and economical to
support the accommodations they require through standards that
technology
developers can adopt and implement across their product
portfolios. In
proposing an Accessibility Working Group to the Free Standards
Group, we
are, therefore, proposing to develop and codify such standards to
the
extent that they are identifiable and implementable through
Application
Binary Interfaces and a set of best practices developed by a
consensus
process among all stakeholders. In particular, we will provide:
-------------- next part --------------

 b. A very brief abstract of the proposed solution, in the form of a
    standard. The abstract should be sufficiently complete to fully
    describe the benefits of such a standard. Initially, industry or
    technical hurdles should be largely ignored. Later revisions may
    take into account more variables.

Since persons with disabilities generally seek to perform the same tasks as all other users of technology, it is prudent, expedient and economical to
support the accommodations they require through standards that technology
developers can adopt and implement across their product portfolios. In
proposing an Accessibility Working Group to the Free Standards Group, we
are, therefore, proposing to develop and codify such standards to the
extent that they are identifiable and implementable through Application
Binary Interfaces and a set of best practices developed by a consensus
process among all stakeholders. In particular, we will provide:

*	A well defined standard for user features that support a
consistant experience across applications. Assistive technologies will
be required to support these features and applications must not defeat
their functionality. For instance, if we say that "Sticky Keys" is a
standard desktop feature, onscreen keyboards can rely on its presence
and be designed accordingly to take advantage of it, and can avoid
conflicting with it.  Likewise applications will then know explicitly
that they must not conflict with or defeat Sticky Keys (or any other
standard accessibility feature).

*	A comprehensive standard for application program interfaces to
support the development of robust assistive technologies across the
heterogeneous free standards environment. It is imperative to provide
for a dynamic nexus between applications and assistive technologies so
that characteristics such as time-out or keystroke event injection can
be adjusted appropriately.