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

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.