Thanks to visit codestin.com
Credit goes to github.com

Skip to content

touch target size not up to a11y standards for DatePicker day period selector. #168245

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.

Sign up for GitHub

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

Jump to bottom
Closed
benjaminwg2017 opened this issue May 2, 2025 · 2 comments
Closed

touch target size not up to a11y standards for DatePicker day period selector. #168245

benjaminwg2017 opened this issue May 2, 2025 · 2 comments
Labels
r: duplicate Issue is closed as a duplicate of an existing issue

Comments

@benjaminwg2017
Copy link

Steps to reproduce

The "AM" and "PM" buttons in the TimePicker dialog have a hard coded height of 39 pt (see image below), which is smaller than the recommended touch target size (see Android a11y guidelines, for example)

Image

This DartPad project displays the TimePicker with the "AM" and "PM" buttons. Inspecting the buttons reveals their size. I believe this is the offending code, hardcoding a height of 80 pixels total for both buttons.

Expected results

The "AM" and "PM" buttons should each have a touch target size of at least 48x48 pixels.

Actual results

The "AM" and "PM" buttons each have a touch target height of 39 pixels only.

Code sample

[

Code sample

[Paste your code here]
](https://dartpad.dev/?id=bd8509ad498a4d44871c78e4c038e418)

Screenshots or Video

No response

Logs

Flutter Doctor output

N/A
@benjaminwg2017
Copy link
Author

This bug affects the internal "chalk" app

@darshankawar darshankawar added the in triage Presently being triaged by the triage team label May 5, 2025
@darshankawar
Copy link
Member

Closing this as duplicate of #158325.

@darshankawar darshankawar added r: duplicate Issue is closed as a duplicate of an existing issue and removed in triage Presently being triaged by the triage team labels May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
r: duplicate Issue is closed as a duplicate of an existing issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@darshankawar @benjaminwg2017