Thread Subject: Re: "closed software"
Note
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: Jim Tobias
Date: Fri, Dec 22 2006 9:00 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jim Tobias: "Re: "closed software""
- Previous message in thread: Peter Korn: "Re: "closed software""
- Messages sorted by: Author | Thread | Date
Gregg wrote:
" The hardware is not closed but the software is. It is not designed to
accept AT.
The fact that at product can be upgraded by its manufacturer with
proprietary software - or even that it allows 3rd party extensions - is a
different issue from whether it works with AT."
As I've posted recently, "closed" means BOTH unable to be controlled from
another, accessible, device like an AT-equipped PC workstation; AND unable
to load and run its own accessibility software.
What does "... works with AT" mean -- only current AT? We should not be
constrained by the current crop of AT. The goal of the regs is to stimulate
native accessibility in products that don't have it right now, and to
stimulate AT where native accessibility is not feasible or reasonable.
Jim Tobias
= EMAIL ADDRESS REMOVED =
- Next message in Thread: Jim Tobias: "Re: "closed software""
- Previous message in Thread: Peter Korn: "Re: "closed software""
WebAIM is an initiative of:
