-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Ion-datetime component is not accessible for the user using keyboard #21553
Comments
From #21602 - The tab navigation / arrow key navigation is not working for ion-datetime. This is an a11y issue. This is reproducible with the example mentioned in ionic site: https://ionicframework.com/docs/demos/api/datetime/index.html?ionic:mode=ios This is item 9 in the document that was shared in the internal Framework Slack channel |
From the users we are working with on this: the ion--datetime, have issues when we try on android device using talkback as well. Navigation to the selection doesn't happen on swipe right.( next element navigation). Navigation from month field to the date field and to the year doesn't happen on swipe right even after selection. The label is not read out as provided. |
Hi, |
Thanks for the issue! |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Bug Report
Ionic version:
[ ] 4.x
[x] 5.x
Current behavior:
The screen reads the ion-datetime component as a button. It’s not reading the associate aria-label or the for it. Also, the date selector is not accessible using only keyboard. It does not receive the focus by default.
Issue is reproducible from the sample implementation also
https://ionicframework.com/docs/demos/api/datetime/index.html?ionic:mode=ios
Refer to item 4 in the document shared in Slack for further details.
https://ionicteam.slack.com/archives/C7CGXAVTL/p1592319616186200
The text was updated successfully, but these errors were encountered: