W3C home > Mailing lists > Public > public-html@w3.org > June 2007

Re: what must be done to expose longdesc? [was Re: fear of "invisible metadata"]

From: gonchuki <gonchuki@gmail.com>
Date: Mon, 25 Jun 2007 10:45:23 -0300
Message-ID: <8320a9390706250645j1ea20562s8983b2210165353a@mail.gmail.com>
To: public-html@w3.org

On 6/24/07, Gregory J. Rosmaita <oedipus@hicom.net> wrote:

>
> the key is that the UA should support LONGDESC natively, and
> allow the user a set of choices about exposing LONGDESC:
>
> * expose in new browser instance
> * expose in new browser tab
> * expose inline (insert content as object)
> * expose inline through the use of IFrame
> * expose the contents of the longdesc document in a side-bar,
>   aligned with the image it describes
>
> and many many others...  if a user knows what to do when
> encountering a long description, then it matters not what
> assisstive technology she is using, for there is an expected
> action in the case of browser x for exposing LONGDESC
>

i'm not getting how breaking navigation via a popup/new tab/iframe OR
breaking the layout by arbitrarily inserting content would increase
accessibility.
Received on Monday, 25 June 2007 15:32:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:01 GMT