Thread Subject: Re: "closedsoftware"
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: David Poehlman
Date: Wed, Jan 03 2007 8:00 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: David Poehlman: "Re: "closedsoftware""
- Previous message in thread: David Poehlman: "Re: "closedsoftware""
- Messages sorted by: Author | Thread | Date
I wonder if there is a distinction between at and accessible it?
Should we not be moving toward accessible it? If I install tiger I
get VoiceOver and all the otheer accessibility feeatures. This seems
to me like accessible IT.
On Jan 3, 2007, at 9:45 AM, Andrew Kirkpatrick wrote:
The Mac OS has an accessibility API that is capable of supporting
assistive technologies - it just happens that Apple made their own, but
an outside company could develop a screen reader or other AT for that
greg, am I to understand then that your #2 excludes the Mac which has
its ownn AT?
2) that products that require productivity (e.g. workstations) need to
be accessible to assistive technologies to allow matching of user
abilities necessary to achieve high levels of productivity.