A compliance checking tool such as Wave http://wave.webaim.org/ reports an error on the month and year selectors, because they have neither label nor title text. The easiest solution would be to add title text, which should of course accommodate localization.
Unfortunately, we don't have this data available for the locales we support. We're in the process of a complete rewrite for datepicker, which uses Unicode's CLDR locale data. However, we're also making substantial changes to the API and functionality and those dropdowns will likely not be built into the core of datepicker. You can see the new API in our planning wiki and the current code in the datepicker branch.
Thanks. I've reviewed the notes on the planning wiki. I don't see the reasoning for not supporting the month and year choosers. How is a user supposed to choose a date several years out, without clicking the nextmonth icon 12*n times? I do see that a keyboard shortcut is proposed, but that isn't really a suitable solution.
That's correct, there will be hooks for building this functionality. I expect that one of the team members will build an extension and we'll use it in a demo. But as of right now, we don't have plans for building this into the core of the widget. While researching calendar navigation, we came across a few different systems and we didn't really want to bless one solution over another. It's entirely possible that this could change before the release though.
Leave a comment on watusiware's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic