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

Opera Re: Conformance evaluations of IBM Home Page Reader

From: Charles McCathieNevile <charles@w3.org>
Date: Mon, 30 Aug 1999 13:47:38 -0400 (EDT)
To: "Gregory J. Rosmaita" <unagi69@concentric.net>
cc: User Agent Guidelines Emailing List <w3c-wai-ua@w3.org>
Message-ID: <Pine.LNX.4.10.9908301346110.22552-100000@tux.w3.org>
Interesting one on Opera. There is a configurable option about what
is presented as a tol tip for links - nothing, the URI, or the title (I
think). I imagine that is what JFW vocalises, but I don't know if there are
multiple ways of doing it.

Haakon might be able to tell us...

Charles McCN

On Mon, 30 Aug 1999, Gregory J. Rosmaita wrote:

  aloha, charles!
  
  you spoke sooth when you wrote:
  >To take a more
  >concrete example, I believe that Jaws for Windows will produce different
  >compliance levels when used with different pieces of software)
  
  one example can be drawn from the amount of information that JFW makes
  available when the user tabs from link to link...  using JFW and MSIE (4 or 5),
  if a TITLE has been defined for a hyperlink, one hears the TITLE text
  announced, whereas in Netscape, the hyperlink text is spoken, even when a TITLE
  has been defined for a hyperlink...  moving from link to link using Opera's
  native keyboard support -- that is, by using the Q or CONTROL+UpArrow keys to
  move to the next link and A or CONTROL+DownArrow to move to the next link -- 
  neither the hyperlink text nor the TITLE, if present, is spoken...  moreover,
  as one moves from link to link, only the content of the first non-active
  element in the current viewport is announced ...  even when using a customized
  script for Opera 3.6 (such as that available from the JFW mailing list's
  hyperarchive) -- so that one can TAB from link to link (a keystroke which is
  second nature to most web surfers), and so that the current viewport is
  automatically spoken -- moving from link to link does NOT cause any aural
  output to be issued by JFW...
  
  as for how this refers to the UAGL, (a) knowing where one is as one moves from
  link to link is the basis of web navigation, and (b) i believe that exposing
  the information contained within a hyperlink is covered by (amongst others)
  Checkpoint 3.2
  
  quote
  3.2 For dependent user agents only. Ensure that the user has access to the
  content of an element selected by the user. [Priority 1] 
  unquote
  
  References
  1. pages that use the TITLE element in hyperlink definitions:
          http://www.w3.org/TR/WAI-WEBCONTENT/
          (refer specifically to the use of TITLE in hyperlinks that refer to
  defined terms)
          http://www.hicom.net/~oedipus/blist.html
          (refer specifically to the introductory text)
          http://www.hicom.net/~oedpus/vicug/index.html
  2. the JFW mailing list pages:
          http://yoyo.cc.monash.edu.au/~nallan/jfw/
  
  gregory
  --------------------------------------------------------
  He that lives on Hope, dies farting
       -- Benjamin Franklin, Poor Richard's Almanack, 1763
  --------------------------------------------------------
  Gregory J. Rosmaita <oedipus@hicom.net>
     President, WebMaster, & Minister of Propaganda, 
          VICUG NYC <http://www.hicom.net/~oedipus/vicug/>
  --------------------------------------------------------
  

--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 Monday, 30 August 1999 13:47:39 UTC

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