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

Re: Amaya conformance to UAGL

From: Charles McCathieNevile <charles@w3.org>
Date: Wed, 25 Aug 1999 13:26:19 -0400 (EDT)
To: Kitch Barnicle <kab42@columbia.edu>
cc: WAI UA group <w3c-wai-ua@w3.org>
Message-ID: <Pine.LNX.4.10.9908251321190.12722-100000@tux.w3.org>
Hmmm. I don't think longdesc is implemented in the 2.1 relase *sigh*.
Anything that is in an attribute is available to the user through the
structure view.

How it works:
I place the cursor at the element I am interested in, open/swap to the
structure view, and it gives me a list of attributes and values. Alternative
technique 1, select the element (press escape in linux), then the attributes
are all available from the attributes menu. For alt, I can also look at the
alternate view, which renders alt text instead of images - a lynx-like view.

All the views are synchronised for navigation (and for editing).

Charles McCN

On Wed, 25 Aug 1999, Kitch Barnicle wrote:

  Charles,
  
  Can you  please elaborate on how you decided that Amaya meets checkpoint 7.2.
  Does Amaya provide access to alt text, titles, long desc and all other "human
  readable" content?
  
  Thanks,
  Kitch
  
  >   7.2 For dependent user agents. Ensure that the user has access to the
  >   content of an element selected by the user.      Amaya is not a
  >   dependent user agent, but satisfies this checkpoint anyway
  

--Charles McCathieNevile            mailto:charles@w3.org
phone: +1 617 258 0992   http://www.w3.org/People/Charles
W3C Web Accessibility Initiative    http://www.w3.org/WAI
MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA
Received on Wednesday, 25 August 1999 13:26:27 UTC

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