Thread Subject: Re: Keyboard 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: David Poehlman
Date: Wed, Sep 12 2007 1:40 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Keyboard proposal"
- Previous message in thread: Gregg Vanderheiden: "Re: Keyboard proposal"
- Messages sorted by: Author | Thread | Date
Ok, Is there an example?
On Sep 12, 2007, at 2:43 PM, Gregg Vanderheiden wrote:
The exception covers things where we do not know how to make non-time
dependent keyboard equivalents.
Basically it is an exception that covers that class of things are
impossible
to do this way.
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of David Poehlman
> Sent: Wednesday, September 12, 2007 10:39 AM
> To: TEITAC Web/Software Subcommittee
> Cc: = EMAIL ADDRESS REMOVED =
> Subject: Re: [teitac-websoftware] Keyboard proposal
>
> I know we discussed this at length, but what is the meaning
> of the exception?
>
> ----- Original Message -----
> From: "Gregg Vanderheiden" < = EMAIL ADDRESS REMOVED = >
> To: "'TEITAC Web/Software Subcommittee'"
> < = EMAIL ADDRESS REMOVED = >
> Cc: < = EMAIL ADDRESS REMOVED = >
> Sent: Wednesday, September 12, 2007 11:32 AM
> Subject: [teitac-websoftware] Keyboard proposal
>
>
> On the keyboard provision
>
>
>
> We need to limit it to devices that have a Keyboard or
> keyboard interface.
>
> We need to allow that some functions may be from other
> mechanical buttons.
>
> Needs to say Keyboard or keyboard interface so that we don't require
> addition of an interface.
>
>
>
>
>
> How about
>
>
>
>
>
>
>
> Where products have a keyboard or keyboard interface , all
> functionality of
> the product operable through the user interface must be
> operable through the
> keyboard or keyboard interface or other mechanical buttons
> without requiring
> specific timings for individual keystrokes. The only
> exception is where the
> underlying function requires input that depends on the path
> of the user's
> movement and not just the endpoints.
>
>
>
> NOTE: A software product that accepts text input would have
> a "keyboard
> interface".
>
>
>
>
>
>
>
> This puts the condition up front so it is easy to see (and
> discard provision
> if not true)
>
> Meets the needs stated above
>
>
>
>
> Gregg
>
> ------------------------
>
> Gregg C Vanderheiden Ph.D.
> Professor - Depts of Ind. Engr. & BioMed Engr.
> Director - Trace R & D Center
> University of Wisconsin-Madison
> < <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848
>
> DSS Player at http://tinyurl.com/dho6b
>
> If Attachement is a mail.dat try <http://www.kopf.com.br/winmail/>
> http://www.kopf.com.br/winmail/
>
> <http://trace.wisc.edu:8080/mailman/listinfo/>
>
>
>
>
>
>
>
>
> --------------------------------------------------------------
> ------------------
>
>
>
- Next message in Thread: Gregg Vanderheiden: "Re: Keyboard proposal"
- Previous message in Thread: Gregg Vanderheiden: "Re: Keyboard proposal"
WebAIM is an initiative of:
