Cally: Accessibility Statement

  The aim is not to give you a full date picker, instead only the lower-level building blocks that allow you to build your own. You likely already have your own inputs, buttons, popover etc components. So why not use them?

Jumping to a specific year is a bit of a painpoint for me.

My component is composed of a text field that accepts dates in many formats. On focus it displays a dropdown with a calendar very similar to Cally (including the next/previous month buttons). As user enters a date in the input field, the calendar updates. The user can also use the calendar to pick a date in the same way as Cally, which updates the input field.

My argument for this being fine is that when a user is entering a date far in the past (or future), such as the date of birth – surely they prefer to enter it in the input field via keyboard, instead of clicking all around the calendar dropdown. Alternatively, perhaps an entirely different component should be used in that use case – perhaps a set of three text fields (limited to numbers).

I semi-regularly get feedback from the business analysts that they would like to have a way to choose the year in the calendar dropdown, but I'm not entirely sure what would be the best way to enable that.

I plan to address this. Issue here https://github.com/WickyNilliams/cally/issues/9

Though I will likely never offer this functionality directly in the components themselves (per the docs: they are not meant to be a complete solution for date pickers, only the lower level parts that are hard to get right). But rather I'll open up the API to allow people to build this stuff themselves. I imagine I'll get this done in the next few days

for mobile browsers, I noticed tab order, tab focus-active paeudostate, and focus fallback (eg what gets focused when a menu closes) to behave differently /incorrectly compared to desktop browser. Also aria-live often does not work on mobile.