Thread Subject: Re: Keyboard operability proposal

From: Gregg Vanderheiden
Date: Thu, May 10 2007 1:05 PM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: Barrett, Don: "Re: Keyboard operability proposal"
• Previous message in thread: Mike Paciello: "Re: Keyboard operability proposal"
• Messages sorted by: Author | Thread | Date

Content that is operable would refer to any aspect of the content that the
person acts on (vs views).

So anything from links to navigating about in a document would apply
(especially navigating about in non markup language content like flash, Java
applet etc).


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Mike Paciello
> Sent: Thursday, May 10, 2007 6:59 AM
> To: 'TEITAC Web/Software Subcommittee'
> Subject: Re: [teitac-websoftware] Keyboard operability proposal
>
>
> I'm not clear on what we mean by the term, "content". I
> haven't seen this brought up in Subpart A discussions (likely
> and oversight on my part). If, however, no clear definition
> exists, then I'm not sure that this guideline is clear.
> Exactly what do we mean by "content that is operable"? Are we
> talking about user interface (which in itself is a challenge
> to clearly define)?
>
>
> Mike Paciello
>
>
> -----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: Barrett, Don: "Re: Keyboard operability proposal"
• Previous message in Thread: Mike Paciello: "Re: Keyboard operability proposal"