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

Re: March 9 Draft of UAAG

From: Ian Jacobs <ij@w3.org>
Date: Mon, 19 Mar 2001 17:07:53 -0500
Message-ID: <3AB68339.D1681971@w3.org>
To: Denis Anson <danson@miseri.edu>
CC: w3c-wai-ua@w3.org
Denis Anson wrote:
> > Abstract:
> > By following these guidelines, developers will create more usable
> > software for all Web users. [DA: Actually, only for users of the
> > browser in question.  Web authoring guidelines improve access for
> > anyone who accesses a page, but UA guidelines only help those using a
> > specific user agent.  What we really mean is that following the
> > guidelines will improve access for all uses of the user agent,
> > including those with disabilities.]
> 
> IJ: I disagree with your interpretation (though I take note of it). Our
> intention is to say: "Accessible design is good design, so if you meet
> these requirements, you will also benefit a larger
> audience than just users with disabilities."
> 
> DA: That part is what I caught, but as worded it seems to say that it
> doesn't make any difference what user agent you are using, all users
> will benefit.  Actually, all users of the compliant user agent will
> benefit, but not all users of the web.

Gotcha. Will fix.
 
> > Guideline 1:
> >
> > People who cannot or do not use a mouse have to be able to operate the
> 
> > user interface with the keyboard, through voice input, a head wand,
> > touch screen, or other device. [DA: In this context, a head-wand is a
> > means of accessing the keyboard, and a touch screen is generally a
> > mouse emulator, so these examples are actually just restating mouse
> > and keyboard.  Why not consider input methods there that do not rely
> > on standard mouse and keyboard presence: such as Morse Code or
> > single-switch scanning. ]
> 
> IJ: The introduction ("Known limitations of this document") explains
> that this document "only includes requirements for
> keyboard, pointing device, and voice input modalities.
> 
> DA: My point is that Morse Code and Single Switch scanning access the
> browser via the keyboard interface.  That is why it's important to
> distinguish between the physical keyboard and a keyboard API: these
> alternative access techniques generate characters, and you need to have
> a keyboard interface to access the browser using such technologies.

The keyboard API requirement is covered by checkpoint 6.7:

  6.7 Implement the operating environment's standard APIs 
      for the keyboard. [Priority 1] 

 - Ian

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783
Received on Monday, 19 March 2001 17:07:57 UTC

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