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

Re: R: NEW: Issue #1544

From: Tina Holmboe <tina@greytower.net>
Date: Sat, 13 Aug 2005 19:03:53 +0200 (CEST)
Message-Id: <200508131703.j7DH3rUm008051@asterix.andreasen.se>
To: w3c-wai-gl@w3.org

On 13 Aug, Bob Regan wrote:

> Interesting stuff. However, we are talking about screen readers, not
> browsers. 

  That's a very interesting comment, on many levels.

  However: what we are talking about is user-agents; the elusive little
  critter which acts on behalf of a visitor to your website.

  We are not, however, discussing a program running on top of a
  user-agent and trying to, by means unknown, access information that
  the UA in question may, or may not, make available.

  If AT foo running on top of UA bar cannot access element baz
  introduced eight years ago, then that is a problem with foo - and
  possibly with bar - but not with baz.

  Yes, using OBJECT, some UAs won't get their hands on the Flash, or any
  interface that said Flash make public. That isn't a problem. The
  *problem* is how to ensure that when this situation arise, the user
  will still get to the information.

  This problem is on the table regardless of whether we refer to ATs or
  UAs; not on whether or not WCAG should endorse browser-specific
  markup.


-- 
 -    Tina Holmboe                    Greytower Technologies
   tina@greytower.net                http://www.greytower.net/
   [+46] 0708 557 905
Received on Saturday, 13 August 2005 17:04:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:39 GMT