Thread Subject: Re: Web Gaps - keyboard operation

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: Robinson, Norman B - Washington, DC
Date: Fri, Jan 12 2007 10:55 AM

Andi,

Sorry I missed the discussion.

I just wanted to point out there are programs that implement textual
equivalents of inherently visual actions used in drawing programs. The
CorelDraw Suite of programs (CorelDraw, CorelPaint) are pretty good
examples. The functions I would normally use with a mouse have text
equivalents through data fields. By example I can draw a circle and
resize it with the mouse or do so by typing in the values for radius or
size in a dialog box when the circle is selected. The same functions for
color, gradients, etc., all have dialog boxes for what one might assume
is inherently visual functions. A classic example where what we call
accessibility has actually increased usability; I can have better
control over design while others benefit from being able to use the
product at all.

I'm wondering about the proposed definition. With realization that many
people have interpreted language based on the semantics, might I ask how
you view the difference between "web content" or "applications"? They
are both software to me and I have to say with the exception of
"discerned textually" the existing 1194.21(a) is clearer.

This is one reason I advocate web content should be reorganized in the
refresh to be a clear subset of software applications. I might be wrong
but I see your definition having to be extended to cover everything
software already covers, and am interested in extending this discussion
in the context of your proposal.

Regards,


Norman B. Robinson
Section 508 Coordinator
IT Governance, US Postal Service
phone: 202.268.8246


-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Friday, January 12, 2007 10:23 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] Web Gaps - keyboard operation



In our discussion yesterday of the keyboard proposal, there were two
issues:

- concern that this may except devices that do not have a keyboard but
which do have keyboard interfaces that may be used by other devices or
AT
software. For example, speech recognition software may use the keyboard
interface for voice navigation.
- confusion over the term "discerned textually". Most interpret this to
mean that free-form drawing functions do not need to be keyboard
operable.
But drawing "objects" such as rectangles or circles can be described by
the
attributes - length, width, radius, position on screen, etc. So these
types
of drawing functions which are optimized for the mouse, do need to be
keyboard operable.

Here's one more attempt at a proposal for a keyboard requirement for
Web:

For Web content or applications that are designed to run on a system
that
has a keyboard interface, product functions shall be executable from a
keyboard interface where the function itself or the result of performing
a
function can be described in words.

Andi

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