WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible Datepicker & NVDA Support

for

From: Chaals McCathie Nevile
Date: May 21, 2016 4:40AM

On Thu, 19 May 2016 17:08:20 -0000, Meacham, Steve - FSA, Kansas City, MO
< <EMAIL REMOVED> > wrote:

> In my organization, I consider date pickers to be a "progressive
> enhancement" and don't even assess them for accessibility, so long as
> the user has the option to use them or ignore them and still specify a
> date.

For precisely the reasons Jonathan suggested, such as knowing what day of
the week some date three months in the future will be, or more generally
being able to annotate dates with more information, I suggest that it is
very helpful to consider the accessibility of date pickers.

I also recognise that they are a very common thing that it is very
difficult to make very accessible.

And since I am offline, I can't look at the specific example for another
day or so, but I'd be interested to see.

I'm really hoping that Web Components will help us fix the problem that
input typeÚte failed to solve in HTML5. Figuring out what makes an
accessible date picker, and finding a *really* good one, gives us insight
into quite a lot of complex problems.

Challenges for the truly geeky - but which become really important when
talking about how to deal with dates.

1. I was at the world finals of ICPC, a programming competition, for the
last week. There was a big poster outside with a mascot-type figure, and
text that amounted, for me who doesn't read the local language's alphabet,
to

17-20 *something* 2559

What does it mean, and how is it relevant to the current discussion?

2. We have fairly reliable information - Shakespeare ;) - that Julius
Caesar was killed on the Ides of March, in 44 BC.

When was that exactly?

3. Why was the anniversary of the October Revolution celebreated in
November?

4. When does the month of Ramadan start and end this year?

cheers

Chaals

>