WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: NVDA and auto-switching of reading modes


From: Jonathan Whiting
Date: Nov 23, 2015 9:55AM

On Mon, Nov 23, 2015 at 1:40 AM, Gijs Veyfeyken < <EMAIL REMOVED> > wrote:

> Until NVDA changes it's default behaviour, you can add a child <div
> role="document"> inside the parent <div role="dialog"> to force NVDA into
> browse mode.

If you're going to add a child with role="document", I would give it
tabindex="0" as well (<div role="document" tabindex="0">). Because NVDA is
in application mode, users will not be able to 'read' into <div> with
role="document", they will only be able to 'tab" to the next element that
can receive keyboard focus. Giving the element tabindex="0" allows users to
navigate into it, which will trigger browse mode. From there they can begin
reading and navigating normally. The one drawback to this approach is that
it does add one extra tab stop, which could be a bit confusing for other
keyboard/screen reader users.

Better than this is to remove role="dialog" if possible, unless it is being
used with a true application dialog. In my experience, this role is seldom
used correctly.


Jonathan Whiting

> Kind regards,
> Gijs
> ---
> Gijs Veyfeyken
> AnySurfer - towards an accessible internet
> http://www.anysurfer.be/en
> Brussels - Belgium
> > > > >