W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 1999

Re: comments on section 4

From: Denis Anson <danson@miseri.edu>
Date: Sat, 20 Feb 99 17:27:25 -0500
Message-Id: <199902202225.RAA01715@www10.w3.org>
To: "Kitch Barnicle" <kitch@afb.org>, <w3c-wai-ua@w3.org>
>
>Section  4.3 Support accessible keyboard input
>
Although it is not obvious, based on my meeting this week with Microsoft, 
we should have another checkpoint:
The user agent should expose the keyboard location to allow keyboard 
emulators equivalent control over keyboard input.

This is not automatic in software.
>
>
>4.3.1 [Priority 2] 
>     Allow the user to configure keyboard access to user agent
>functionalities. Configuration includes the ability to specify single as
>well as multi-key access. 
>
>
>4.3.2 [Priority 2] 
>     Ensure that user can find out about all keyboard bindings. 
>4.3.4 [Priority 3] 
>     Display keyboard bindings in menus. 
>
>KB: We discussed on the telecon that checkpoint 4.3.4 is covered by
>checkpoint 4.3.2.
>
>
>4.4.12 [Priority 1] 
>     Allow the user to turn on and off support for spawned windows. 
>
>KB: I know that spawned windows are a problem but I am not sure if it is a
>priority 1 problem. What do people think? Is it important to let the user
>turn off this feature or should the user agent just make sure that the user
>is notified when a new window is spawned?
>
>
I agree that this should probably be Priority 2.  Spawned windows may 
confuse some groups, but in general, confusion does not preclude access, 
merely makes it difficult.

Denis Anson
Received on Saturday, 20 February 1999 17:26:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:48:48 GMT