WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Document within a document: how to mark up?

for

From: Isabel Holdsworth
Date: Jun 21, 2019 8:21AM

Thanks Glen. We're constrained to displaying both the main document
and the supplementary content on the same page - we can't open new
tabs.

The content panel feels like something other than a dialog to me. For
me dialogs are for asking a quick question or displaying a
confirmation message, and their mission is to be acted upon and
dismissed. I prefer dialogs to be modal. It's too easy for
screenreader users to get lost on pages that have non-modal dialogs on
them, especially if there could potentially be more than one visible
at a time, and if they could contain a significant amount of content.
The boundary between non-modal dialogs and main content is too soft. I
want these supplementary documents to be fenced off somehow, so that
screenreader users move into and out of them by choice rather than by
accident.

Cheers, Isabel

On 21/06/2019, glen walker < <EMAIL REMOVED> > wrote:
> For a low vision or visually impaired screen reader user, whether the
> non-modal dialog is an overlay or a separate tab wouldn't seem to make much
> difference. You'd still have to toggle between the "dialog" and the main
> page. Toggling between tabs is already a known keyboard interaction (such
> as ctrl+tab) whereas toggling between windows is not.
>
> For a sighted user, having the dialog on the same page would seem to be an
> advantage. You wouldn't need to toggle as often.
>
> As long as it's obvious and well documented on what keys are used to switch
> between the non-modal and the main page (and how to move the non-modal), I
> don't see this as a problem.
>
> If it were allowed, it might be nice to have an option on the non-modal to
> "undock" it so that it becomes a separate tab. (And be able to re-dock it
> back to the main page.) That way the user gets to decide if they want a
> floating non-modal or a separate tab.
> > > > >