Thread Subject: Re: Keyboard operability 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: Fri, May 11 2007 7:00 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Sean Hayes: "Re: Keyboard operability proposal"
- Previous message in thread: Gregg Vanderheiden: "Re: Keyboard operability proposal"
- Messages sorted by: Author | Thread | Date
so if using a stylus I gotta be fast?
----- Original Message -----
From: "Gregg Vanderheiden" < = EMAIL ADDRESS REMOVED = >
To: "'TEITAC Web/Software Subcommittee'"
< = EMAIL ADDRESS REMOVED = >
Sent: Thursday, May 10, 2007 9:16 PM
Subject: Re: [teitac-websoftware] Keyboard operability proposal
That works well for both.
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Barrett, Don
> Sent: Thursday, May 10, 2007 3:14 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Keyboard operability proposal
>
> Couldn't we just substitute "user interface" for content:
>
> All functionality of the user interface is operable through a
> keyboard interface without requiring specific timings for
> individual keystrokes, except where the underlying function
> requires input that depends on the path of the user's
> movement and not just the endpoints.
>
>
>
> 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 Andi Snow-Weaver
> Sent: Wednesday, May 09, 2007 3:06 PM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] Keyboard operability proposal
>
>
> Here is the latest keyboard operability provision from WCAG
> 2.0. We discussed this briefly in the subcommittee meeting
> today and there were no objections. Please review. If there
> are no objections on the mailing list, we will insert this
> into our 3rd draft submission as a recommended wording change
> for 1194.21 (a) and as a new provision for 1194.22.
>
> All functionality of the content is operable through a
> keyboard interface without requiring specific timings for
> individual keystrokes, except where the underlying function
> requires input that depends on the path of the user's
> movement and not just the endpoints.
>
> * Note: This exception relates to the underlying
> function, not the input technique. For example, if using
> handwriting to enter text, the input technique (handwriting)
> requires path dependent input but the underlying function
> (text input) does not.
> * Note: This does not forbid and should not discourage
> providing mouse input or other input methods in addition to
> keyboard operation.
>
> Andi
>
>
- Next message in Thread: Sean Hayes: "Re: Keyboard operability proposal"
- Previous message in Thread: Gregg Vanderheiden: "Re: Keyboard operability proposal"
WebAIM is an initiative of:
