We are currently having a lot of accessibility issues with the currently used datepicker, which is from Angular UI Bootstrap. The sources were pulled over which makes updating currently a miss. Also we would need to refactor large parts of the code that we pulled over to modify the custom keyboard controls (using arrow keys to navigate), to be accessible with that component.

Since we are currently building the UI framework with React components, this might be the perfect time to move to a React date picker, and if we need to fix accessibility issues, directly fix them in the new component (or upstream if we are using a library).

Since we would prefer using regular dependencies (for maintenance reasons) instead of pulling source code over, we "just" need to decide what a good dependency would be, and maybe create a wrapper component in Kibana for it. That way we would be free to change the underlying implementation at any time as long as the wrapper has a stable API.

I've previously used react-datepicker which is a pretty solid library, but unfortunately does neither provide any accessibility right now. I would prefer having a stable and solid library at the moment without a11y and providing this upstream instead of having a maybe less popular, less maintained library, that HAS a11y.