a11y

[wwilsman]

Currently not doing anything for accessibility.

• [ ] How do various native datepickers behave for screen readers?
• [ ] Keyboard navigation
• [ ] Add accessibility markup to default template / Programmatically add it at render
• [ ] Handle input value changes (disallow/parse on blur)

[wwilsman]

@Robdel12

[Robdel12]

Oof man, we're going to have our work cut out for us. When I was going through improving pikadays a11y really actually needed a big big refactor.

Thankfully we don't have semver to worry about. Step 1 is using it with a screen reader. We'll see how far we have to go :p

[wwilsman]

@Robdel12 😉

[Robdel12]

Is this shipped?

[wwilsman]

As a beta, and apparently this repo is out of date with NPM.

[Robdel12]

hahahaha where does this fall on the priority list? Should pair on it sometime

[wwilsman]

A11y, probably not as high of a priority as me needing to update deps, move to rollup, and cut a new release. But we can turn this into a accessible component that can live alongside Dropkick