E-mail List Archives
Re: Modal close button not focusable; ESC works
From: Birkir R. Gunnarsson
Date: Jun 22, 2016 4:10PM
- Next message: Alan Zaitchik: "Re: Headings: requirements vs best practices"
- Previous message: Jonathan Avila: "Re: FW: non-underlined link - will bolding meet contrastrequirement?"
- Next message in Thread: Maxability Accessibility for all: "Re: Modal close button not focusable; ESC works"
- Previous message in Thread: Jonathan Avila: "Re: Modal close button not focusable; ESC works"
- View all messages in this Thread
My prime argument for this is lack of accessibility on mobile.
A CSUN presentation I did with my colleague CB Averitt started with
this very example http://whoseline.a11yideas.com
(yes, it is awkward, but if you are using iOS with Voiceover you can't
get past the pop-up" dialog that is displayed when you click the
"Start presentation" link).
There may be some variations on close buttons that, while not keyboard
accessible, are operable on a touch-screen. If so, and if escape key
works on a keyboard, I would have a hard time doing more than making
it a best practice issue.
I think NVDA needs to consider a different key combination for
switching between interaction modes, at least in the long-term,
because the use of escape key in this situation has caused all sorts
of confusion for end users.
Users often do not know that the NVDA key plus space bar does exactly
what they want.
On 6/22/16, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> Would love to read any thoughts you folks might have. Feel free to post
>> here, or on the issue itself.
>
> If in focus mode -- NVDA may turn off focus mode when escape is pressed. I
> haven't tested this with the particular implementation -- but the fact that
> it uses escape could be problematic if escape doesn't close the dialog. It
> could also go the other way the user may expect to turn off focus mode and
> may dismiss the dialog by accident. Something to look into.
>
> The other possibility might be with mobile where there is no escape button
> on the on-screen keyboard -- but it's possible that the close button may
> still be usable on mobile even if it is not in the focus order -- so that
> may not be an air tight argument either.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> <EMAIL REMOVED>
> 703.637.8957 (Office)
>
> Visit us online: Website | Twitter | Facebook | Linkedin | Blog
> Check out our Digital Accessibility Webinars!
>
>
>
- Next message: Alan Zaitchik: "Re: Headings: requirements vs best practices"
- Previous message: Jonathan Avila: "Re: FW: non-underlined link - will bolding meet contrastrequirement?"
- Next message in Thread: Maxability Accessibility for all: "Re: Modal close button not focusable; ESC works"
- Previous message in Thread: Jonathan Avila: "Re: Modal close button not focusable; ESC works"
- View all messages in this Thread