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: Peter Korn
Date: Fri, Jan 12 2007 11:05 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Andi Snow-Weaver: "Re: Web Gaps - keyboard operation"
- Previous message in thread: Robinson, Norman B - Washington, DC: "Re: Web Gaps - keyboard operation"
- Messages sorted by: Author | Thread | Date
Hi Andi,
I think this is a good draft of new language. I wonder about ending it
with "described succinctly in words", or "describe precisely in words",
or some such. My concerns are:
1. folks have been describing pictures for years, just not with
sufficient precision to completely and precisely reproduce them
2. anticipating questions I'll get from developers who need advice on
implementing 508 support, I foresee a lot of arguments about what is and
isn't describable in words (mind you, this is the same problem we have
now with "discernible textually").
Regards,
Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.
> 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
>
>
- Next message in Thread: Andi Snow-Weaver: "Re: Web Gaps - keyboard operation"
- Previous message in Thread: Robinson, Norman B - Washington, DC: "Re: Web Gaps - keyboard operation"
WebAIM is an initiative of:
