Thread Subject: Re: API Requirements proposal

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: terry.weaver@gsa.gov
Date: Tue, Apr 03 2007 10:10 AM

Regarding accessible calculators, it may be that the horse is already out
of the barn. In my inbox today, I received the email below. It would
appear to address calculators as a closed system.

ViewPlus announces the third edition of their Audio Graphing Calculator!
The fully-accessible, scientific graphing calculator for Windows® Purchase
the full version for $295.00 or upgrade from AGC 2.0 to the most recent
version of 3.0 for $195.00.
Components of AGC 3.0:
Describing of a graph shape using audio tones and cues
Fully speaking menus with adjustable voice volume and speed
Scalable visual display
Keyboard navigation
Options for tactile output of graphs
New features include:
Advanced matrix functions
Ability to display multiple graphs and find intersections
Increased functionality of the expression evaluator
Increased quantity of statistical functions
Windows Vista Compatible! *Shipping April 9th* For more information or to
download a 30-day demo of the AGC, please visit www.viewplus.com




"Peter Korn" < = EMAIL ADDRESS REMOVED = >
Sent by: = EMAIL ADDRESS REMOVED =
04/03/2007 03:12 AM
Please respond to
"TEITAC Web/Software Subcommittee" < = EMAIL ADDRESS REMOVED = >


To
"TEITAC Web/Software Subcommittee" < = EMAIL ADDRESS REMOVED = >
cc

Subject
Re: [teitac-websoftware] API Requirements proposal






Hi Gregg,

> Do we want to say something about being on a system that supports AT or
> something? Else this could get applied to phones, or even advance
> calculators?
>

Right now this is part of 1194.21 "Software applications and operating
systems". That title is one way of distinguishing this from phones &
calculators. I know the General group is looking at attribute-based
groupings. I believe most (all?) of us in this group had desktop
computing systems in mind when we crafted this language.

"on a system that supports AT" is I think tricky language (with a hole
in it you could drive something large through). One could make a
credible argument that Windows 3.1 and Macintosh (through System 7 at
least) and many other desktop systems that ran AT were systems that
"support AT" - AT was done in spite of them. A number of cell phones
today might be likewise in that camp.

At the same time, if some AT vendor somewhere managed to reverse
engineer something (even an advanced calculator), would that mean that
from that day forward no applications could be acquired by the Federal
Government for that calculator unless such software met everything in
(the new) 1194.21(d)? The existence of AT on a given device isn't the
best measure of this either.


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.

>
> Nicely done.
>
>
> Gregg
> -- ------------------------------
> Gregg C Vanderheiden Ph.D.
>
>
>
>
>> -----Original Message-----
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
>> Of Andi Snow-Weaver
>> Sent: Monday, April 02, 2007 6:57 PM
>> To: = EMAIL ADDRESS REMOVED =
>> Subject: [teitac-websoftware] API Requirements proposal
>>
>>
>> The API requirements sub-group is ready to put forward a
>> proposal for modifications to 1194.21 (c), (d), and (f). [1]
>>
>> Please review this proposal and provide your comments and
>> feedback via the mailing list. We will add this to the agenda
>> for Wednesday's meeting.
>>
>> [1]
>> http://teitac.org/wiki/Web_and_Software:_Accessibility_API_Req
>> uirements_Draft_3
>>
>> Andi
>>
>>

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