WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Semi-inert modals

for

From: Kian Badie
Date: Apr 4, 2022 4:09PM

Hello,

Thank you very much for the very detailed explanation and examples! They
help a lot. I think I also want to make this a self-contained dialog and
manage keyboard focus to be trapped in the modal while it is open.

If mouse users are able to interact with content outside the modal (like
the header and footer), would that be considered inaccessible since it is
not the same experience? A keyboard user would have to close the dialog
before having access to the header/footer since keyboard focus would be
trapped within the self-contained dialog. It is indeed a different
experience with an extra step of closing the dialog to get to the
header/footer, but it seems to me that both experiences are accessible even
though they are different.

Thank you,
Kian Badie

On Mon, Apr 4, 2022 at 10:05 AM Bryan Garaventa via WebAIM-Forum <
<EMAIL REMOVED> > wrote:

> Hi,
> It depends on what you mean by support.
>
> The accessibility API can map the dialog element to the dialog role, which
> will provide the same feedback if the dialog is properly labelled. This is
> how an H2 element has the same feedback as role="heading" + aria-level="2",
> and to screen reader users there is no difference.
>
> However, for this to truly be accessible, a dialog has to manage focus
> appropriately, which means that scripting is needed to do so. For the
> browsers to do this automatically, they would have to guess at what is
> meant to receive focus within the dialog when it is rendered, which will
> likely conflict with actual focus handling that is built into the dialogs.
> It may be possible to override this to some extent, but doing so would
> likely be very buggy.
>
> Bryan Garaventa
> Principal Accessibility Architect
> Level Access, Inc.
> <EMAIL REMOVED>
> 415.624.2709 (o)
> www.LevelAccess.com
>
>