Thread Subject: Re: FW: Keyboard operabilityproposal(fromTomBrett)
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: Barrett, Don
Date: Tue, May 15 2007 2:05 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: FW: Keyboard operabilityproposal(Forwardednote from Randy Marsden)"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
Sorry Greg, I was quoting from a prior post which wanted to reword the
keyboard operability standard. I was saying that requiring an alternate
input for tasks involving path-dependent input as the rewording
suggested didn't make sense to me.
Don Barrett
Section 508 Coordinator
U.S. Department of Education
(202)-205-8245
= EMAIL ADDRESS REMOVED =
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gregg
Vanderheiden
Sent: Tuesday, May 15, 2007 3:56 PM
To: 'TEITAC Web/Software Subcommittee'; = EMAIL ADDRESS REMOVED =
Subject: Re: [teitac-websoftware] FW: Keyboard operability
proposal(fromTomBrett)
Don't understand "an alternative method for this type of input must be
provided."
Regarding your other question. - cameras are not being used for
gesture
input and we will see much more of that in the future. Also
accelerometers
on hand held devices.
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> Barrett, Don
> Sent: Tuesday, May 15, 2007 2:48 PM
> To: = EMAIL ADDRESS REMOVED = ; TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] FW: Keyboard operability proposal
> (fromTomBrett)
>
> "an alternative method for this type of input must be provided."
>
> That may be setting the bar way too high; if a path is required, and
> the task cannot be done from the keyboard, what, besides the mouse,
> could possibly serve as an alternate input? If we just mean the
> mouse, then we are stating the obvious.
>
- Next message in Thread: Gregg Vanderheiden: "Re: FW: Keyboard operabilityproposal(Forwardednote from Randy Marsden)"
- Previous message in Thread: None
WebAIM is an initiative of:
