Thread Subject: Re: FPC - USERS' AT
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Gregg Vanderheiden
Date: Mon, Jun 04 2007 10:40 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Peter Korn: "Re: FPC - USERS' AT"
- Previous message in thread: Peter Korn: "Re: FPC - USERS' AT"
- Messages sorted by: Author | Thread | Date
But if we do we also reduce the number of people who can access to less than
So both solutions are not acceptable. We are put in a really &^#@$%&
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> Peter Korn
> Sent: Monday, June 04, 2007 11:22 AM
> To: TEITAC General Interface Accessibility Subcommittee
> Subject: Re: [teitac-general] FPC - USERS' AT
> Hi Gregg,
> > Which users' AT?
> > If "users' AT" means ALL users' AT it sets unreasonable
> limitations on
> > technologies that can be used.
> > If "users' AT" means only the best AT out there it
> unreasonably limits
> > access to government information to just the small
> percentage with the
> > best AT.
> One real problem - if we restrict what can be deployed to the
> public to something other than what the latest AT supports
> (let us presume to pick a number, only those features that is
> support by AT that has been in on the market for 1 year),
> then we remove a major incentive for AT vendors to support
> new technologies, approaches, etc.
> The AT industry has historically trailed new technology -
> typically supporting Web techniques and applications only
> when a critical mass / large enough market share has
> developed. There are a variety of reasons for this -
> including how hard it is to develop AT in a world without
> good support for AT-IT interoperability. Nonetheless, it is a
> market reality today.
> There is a real danger that we will hinder the development
> and deployment of new and accessible techniques if use any
> test that requires compatibility with AT deployed in the field.
> The situation we have today isn't great either - the
> proliferation of inaccessible techniques (e.g. AJAX without
> support for WAI ARIA) and the lag we have today in making
> them accessible. Frankly the only way I see to address this
> is to push new development as much as possible to develop and
> use accessibility services for AT-IT interoperability (as we
> are doing in our drafts).
> Peter Korn
> Accessibility Architect,
> Sun Microsystems, Inc.