Thread Subject: Re: 1194.22(b) in Group A: Re: JimTobias'commentabout requiring AT

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: Jessica M. Brodey
Date: Thu, Oct 19 2006 9:50 PM

Tamas writes:
"An other thought I have about operating systems, is that all operating
systems can be classified as software, but not all softwares are operating
systems. Thus, operating systems should be compliant with all standards,
after all, they are also constitute as a government purchase. I would like
to see some standards, which set the foundation of a solid and accessible
operating systems, so that all applications and assistive technologies would
be able to run on them."

Interoperability is certainly a key issue for ATIA. For us, we would not
necessarily argue to natively building in all accessibility features all the
time - at times it is appropriate for features to be add-on assistive
technology and sold separately. However, it is necessary that all systems
and software be designed so that AT can easily be added on to the system so
that it is fully integrated and interoperable. Today, it is not easy to
plug in an alternate computer access device (switch, sip and puff, eye
tracker) and be certain that it will consistently control every piece of
software in the same manner that a mouse works. As we move forward, it will
be critical for us to determine which accessibility features are critical
for access, and what features and components are at the core of ensuring
interoperability with AT.

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University