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: Kathleen Wahlbin
Date: Thu, May 10 2007 8:15 AM

We could start by defining "content" using the Wikipedia definition
(http://en.wikipedia.org/wiki/Content)



Content can refer to:



Information and experiences created by individuals, institutions and
technology to benefit audiences in contexts that they value.

* Raw content is content in format that is detectable by an
observer.

* Sections, parts or the whole of a document regardless of the
medium.



...



Online, content is generally referred to as the elements on a web page.
This could include text, graphics, clip art, photos, videos, podcasts,
wav files, hyperlinks, code or any value-added substance that a visitor
to the web page would benefit from. ... It is generally believed by
Internet marketers that text and graphics benefit website visitors more
than anything else.



http://en.wikipedia.org/wiki/Web_content

Web content is the textual, visual <http://en.wikipedia.org/wiki/Visual>
or aural <http://en.wikipedia.org/wiki/Aural> content
<http://en.wikipedia.org/wiki/Content> that is encountered as part of
the user experience on websites <http://en.wikipedia.org/wiki/Website> .
It may include, among other things: text, images
<http://en.wikipedia.org/wiki/Digital_image> , sounds
<http://en.wikipedia.org/wiki/Digital_sound> , videos
<http://en.wikipedia.org/wiki/Videos> and animations
<http://en.wikipedia.org/wiki/Animations> .



Kathy



Kathleen Wahlbin, Director, User Experience

Mindshare Interactive Campaigns, LLC

1717 W. 6th Street, Suite 270

Austin, TX 78703

tel 512.350.2476 fax 512.323.5044

www.mindshare.net / www.rampweb.com



-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andrew
Kirkpatrick
Sent: Thursday, May 10, 2007 8:59 AM
To: = EMAIL ADDRESS REMOVED = ; TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Keyboard operability proposal



Mike,

Thank you for asking this. I feel that I've asked this question several

times and have not yet heard an answer. I think that our work to

harmonize the 1194.22 web standards with the W3C's Web Content

Accessibility Guidelines will add to the confusion since the proposal

has been to have a section on content that is separate from the

harmonized web standards.



Please, can someone define "content", preferably without relying on "we

know it when we see it" as part of the definition?



Thanks,

AWK







> -----Original Message-----

> From: = EMAIL ADDRESS REMOVED =

> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf

> Of Mike Paciello

> Sent: Thursday, May 10, 2007 7: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

>

>

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University