W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2000

Issues raised by Karl Dubost about UAAG 1.0

From: Ian Jacobs <ij@w3.org>
Date: Wed, 08 Nov 2000 16:55:58 -0500
Message-ID: <3A09CBEE.2C757911@w3.org>
To: w3c-wai-ua@w3.org

I'm forwarding an issue raised by Karl Dubost (of the W3C Team)
of the 23 October 2000 last call document.

1)  1.2 Use the standard input and output APIs of the operating system.

Issue: What if the standard input and output APIs "do the wrong thing"
       or lead to accessibility problems?

IJ: This seems very similar to previous questions about following
    system conventions. In the past, we've addressed this by saying
    something along the lines of "unless they cause known accessibility
    problems." One proposal is to add this. Another is to leave it
    as is and say that this is an OS problem.

Also, a suggested technique for 7.1:

   I suggest a double or triple mechanisms for navigation between
        - You have multiple windows open, ex: ctrl + Alt + tab to 
          switch between windows
        - You have frames, ex: ctrl + tab to select the right frame.
        - You are in a frame or a window, ex tab to select the link or
the box.

   So, people will not have to pass all links of the first window/frame 
   before to have the right thing.

 - Ian

[1] http://www.w3.org/TR/2000/WD-UAAG10-20001023/
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783
Received on Wednesday, 8 November 2000 16:55:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:28 UTC