WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: jQuery Datepicker - expected kb behavior?

for

From: Jeff Gutsell
Date: Oct 12, 2018 2:30PM

I am a self-taught scripter, and perhaps I am missing something about using
Control plus arrow keys. A fundamental part of the keyboard accessibility
described by the W3C is using arrow keys to move focus. I don't recall the
W3C ever mentioning the need for the control key.
A :"keydown" event that wants to move focus should include the
preventDefault() method to avoid scrolling the page while the focus is
within the widget. That is how the W3C aria example for popup menus works.


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
Of glen walker
Sent: Thursday, October 11, 2018 12:45 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] jQuery Datepicker - expected kb behavior?

I don't know if ctrl+arrow is the "typical" way to navigate through a
calendar but I've found that if unmodified arrows don't work, then I try
ctrl+arrows.

Of course, with a screen reader running, the unmodified arrow keys will
walk the accessibility tree and not navigate the calendar unless the
calendar goes into forms/application mode, so perhaps that's why some
calendars choose to use ctrl+arrow to navigate.