[Enhancement] Keyboard enabled calendar component

[alxzak]

Describe the enhancement

I would like to use keyboard shortcuts in the calendar component.

Describe the solution you'd like

I like to use TAB to tab from prev month to next month to day selector.
And in the day selector i would like to use the arrow keys on my keyboard.

---

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Refinement

• Request that the issue is UX refined; do not proceed until this is done.
• Request that the issue is tech refined; do not proceed until this is done.

Implementation

The contributor who wants to implement this issue should:

• Make sure you have read: "Before you get coding".
• Signal to others you are working on the issue by assigning yourself.
• Create a branch from the master branch following our branch naming convention.
• Publish a WIP implementation to Github as a draft PR and ask for feedback.
• Make sure you have implemented tests following the guidelines in: "The good: Test".
• Update the cookbook with examples and showcases.

Review

Once the issue has been implemented and is ready for review:

• Do a self-review.
• Create a pull-request. If you created a draft PR during implementation you can just mark that as "ready for review".

[alxzak]

deadline 22/9

[jkaltoft]

For inspiration, see examle: https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/datepicker-dialog.html

[jkaltoft]

Being able to interact with a datepicker (Calendar) using a keyboard is one thing, and it will not make it accessible in itself.

I suggest we also address other aspects of this component/widget such as making sure the markup is semantic and descriptive and that we enhance it to an appropriate degree.

[MadsBuchmann]

Hey team! Please add your planning poker estimate with ZenHub @jkaltoft @RasmusKjeldgaard

[stale]

This issue has been automatically marked as stale because of no recent activity. It will be closed in 10 weeks if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed due to inactivity. Please open a new issue if it becomes relevant again.