WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Modal Dialog Content Not Being Read

for

From: Birkir R. Gunnarsson
Date: Jul 27, 2016 12:07PM

I am awfully stubborn with the dialog role thing.
I personally don't like NVDA automatically switching into forms mode
when inside a dialog.

But the fact is that authors can only use the most appropriate
role/markup for the job, then leave the handling of that markup to the
assistive technology.
That's why I am in principal against using role="region" or the
document role specifically to cancel the NVDA forms mode interaction
with dialogs.
NVDA might have user feedback I am not aware of, or other reasons why
they do not change this functionality on their end.

We are creating standards precisely to get away from authors being
exposed to the whims of a particular user agent. The more we enforce
that authors follow that standard, and ensure that the user agents
take advantage of that markup and translate it into a better
experience for the people, the faster we will get to a more accessible
world, at least in theory.
I know teling a frustrated user who is not able to access an important
alert about his online statement today that he just has to file an
issue with his screen reader vendor and he will likely be able to see
the alert in November is not exactly helpful.
That is the dilemma that us accessibility folks often find ourselves in.
Do we fix it with 6 layers of duct tape today, or do we give ourselves
time to go to Home Depot to get a 2 by 4 and the tools to fix it
proper.
Honestly, we keep having to do a bit of both.
Cheers



On 7/27/16, Bryan Garaventa < <EMAIL REMOVED> > wrote:
> No worries, we all make mistakes :)
>
>
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> <EMAIL REMOVED>
> 415.624.2709 (o)
> www.SSBBartGroup.com
>
>
>