WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: in a modal dialog can the tab focus go to the browser UI?

for

From: chaals@yandex-team.ru
Date: Feb 1, 2017 3:19AM

Note also that this is a current issue for the HTML spec: https://github.com/w3c/html/issues/773

cheers

31.01.2017, 23:23, "Lucy Greco" < <EMAIL REMOVED> >:
> hello:
>  i think it is a best practice to restrict focus to the dialog if the
> dialog has actions that need to happen before the user can move on. the
> user will become confused if they are interacting with a dialog and then
> the contents out side the dialog start coming up. also i have seen the
> behavior wear the dialog comes up but the screen reader is focused on the
> contents behind the dialog visually so that is an other reason to restrict
> focus. This situation is vary bad if the screen reader user is trying to
> get support and the sited person does not know they are on hidden
> content.lastly the one point no one has made is that once the user is done
> in the dialog you must be sure to bring them back to the write place i.e.
> wear they initiated the dialog or on the write place of the new page if a
> new page is generated from the dialog.
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
> On Tue, Jan 31, 2017 at 10:27 AM, JP Jamous < <EMAIL REMOVED> > wrote:
>
>>  Answers below.
>>
>>  -----Original Message-----
>>  From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>>  Behalf Of Ramakrishnan Subramanian
>>  Sent: Tuesday, January 31, 2017 12:20 PM
>>  To: <EMAIL REMOVED>
>>  Subject: [WebAIM] in a modal dialog can the tab focus go to the browser UI?
>>
>>  Dear members,
>>  I kindly request your inputs on the following scenario as per the WCAG
>>  guideline and aria authorization practice:
>>
>>  Actual behavior:
>>  In a modal dialog while navigating using tab /shift tab keys: though the
>>  focus is trapped inside the dialog, when we hit tab key from the last
>>  focusable element inside the dialog, the focus is going to the browser UI.
>>
>>  That's typical as that is the standard behavior unless you restrict the
>>  user to the modal.
>>
>>  Expected behavior:
>>  1. When we hit tab from the last focusable element, the focus should
>>  go to the first focusable element inside the dialog.
>>  2. when we hit shift tab from the first focusable element, the focus
>>  should go to the last focusable element inside the dialog.
>>
>>  You can do the above with ARIA. You won't be violating any WCAG criteria.
>>  Unless you provide a Close button to allow the user to return to the
>>  browser UI. If you do not provide a Close button, you won't be in
>>  compliance with WCAG level A criteria.
>>
>>  Is this only a best practice? Or
>>  Is this mandatory to pause wecag guidelines?
>>
>>  : should we flag this as bug as per wcag and aria authorization?
>>  If the developers feel that this is something which is a browser behavior
>>  which need not be altered.
>>  Is that fine?
>>
>>  Thanks and Regards,
>>  Ramakrishnan
>>  >>  >>  at http://webaim.org/discussion/archives
>>  >>
>>  >>  >>  >>  >
> > > > -- 
Charles McCathie Nevile - standards - Yandex
<EMAIL REMOVED> - - - Find more at http://yandex.com