Thread Subject: Re: Reminder for Conference Call Today
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: Debbie Cook
Date: Tue, Jan 23 2007 6:30 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Gregg Vanderheiden: "Re: Reminder for Conference Call Today"
- Messages sorted by: Author | Thread | Date
Thanks for catching that. And, I have other edits from today's discussion
that I will put on the WIKI so that section will change.
----- Original Message -----
From: "Gregg Vanderheiden" < = EMAIL ADDRESS REMOVED = >
To: "'TEITAC self contained/closed products subcommittee'"
< = EMAIL ADDRESS REMOVED = >
Sent: Tuesday, January 23, 2007 3:18 PM
Subject: Re: [teitac-closed] Reminder for Conference Call Today
Is there a typo here?
* Further discussion needed on categorization of products for which there is
an API but for which there is not compatible or available AT. The product is
not inaccessible, but does not meet access requirements since it is not
useable by people with disabilities.
If accessibility means 'operable by people with disabilities'
Then if there is no AT (and AT is only way to access) then I would think it
would fail the definition of accessible. So the product would not be
accessible and would not meet access requirements.
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> Debbie Cook
> Sent: Tuesday, January 23, 2007 11:08 AM
> To: TEITAC self contained/closed products subcommittee
> Subject: Re: [teitac-closed] Reminder for Conference Call Today
> I am also going to post here what I attempted to post to the
> WIKI. When I click on the Edit link I get an error so I
> assume there's a system rpoblem.
> Here's the summary I will post hwen it's working again:
> == Summary of Discussions as of January, 2007==
> * The terms Closed and Self-contained are two distinct
> identifiers and pertain to product characteristics or product
> functions rather than to a specific category of IT products.
> * A Self-contained product or product function is one that
> has built-in accessibility features that comply with
> appropriate 508/255 requirements.
> The product may also be accessible through AT for some aspect
> of operation.
> For example, a voting machine which for security reasons does
> not allow end users to install a screen reader or magnifier
> (these features are built in) but does allow a user to
> connect a switch device (AT) to the hardware for input.
> * A closed product or function is one that is not
> self-contained (does not have built-in accessibility), or
> cannot work with available AT (for policy or design reasons).
> Development is fluid, and a product or feature which is
> "closed" to AT may become open by deployment of
> self-contained accessibility or through compatibility with
> available AT.
> * Further discussion needed on categorization of products for
> which there is an API but for which there is not compatible
> or available AT. The product is not inaccessible, but does
> not meet access requirements since it is not useable by
> people with disabilities.
> ----- Original Message -----
> From: "Debbie Cook" < = EMAIL ADDRESS REMOVED = >
> To: < = EMAIL ADDRESS REMOVED = >
> Sent: Tuesday, January 23, 2007 8:35 AM
> Subject: [teitac-closed] Reminder for Conference Call Today
> Time: 4:00 eST
> Phone: 408-974-8478
> code: 1212
> FEDRCC: 643194.
> We will discuss the voting access guidelines in relation to other
> self-contained products.
> Deb & Mary Beth
- Next message in Thread: None
- Previous message in Thread: Gregg Vanderheiden: "Re: Reminder for Conference Call Today"