Repository navigation
[Google3 Bug]: State information not announced for AM/PM in Material DateTimePicker #173302
Description
Help us understand the severity of this issue
- causing severe production issues e.g. malfunctions or data loss
- blocking next binary release
- blocking a client feature launch within a quarter
- nice-to-have but does not block a launch within the next quarter
Steps to reproduce
- Turn on Voicover
- Navigate to the DateTimePicker
- Select a date
- Navigate to the AM/PM buttons and select one of them
Expected results
VoiceOver announces the AM/PM buttons with state information (e.g. selected, PM, button).
Actual results
VoiceOver announces the AM/PM buttons without state information.
Code sample
Code sample
import 'package:flutter/material.dart';
void main() {
runApp(MyApp());
}
class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return MaterialApp(
debugShowCheckedModeBanner: false,
home: Scaffold(body: Center(child: MyWidget())),
);
}
}
class MyWidget extends StatelessWidget {
@override
Widget build(BuildContext context) {
WidgetsBinding.instance.addPostFrameCallback((timestamp) {
showTimePicker(
context: context,
initialTime: TimeOfDay.now(),
orientation: Orientation.portrait,
);
});
return Container(height: 300, width: 100);
}
}Screenshots or Video
Logs
No response
Flutter Doctor output
n/a
Metadata
Metadata
Labels
High-priority issues at the top of the work listAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)Works on one platform but not anotherVarious Google teamsDate or time picker widgetsFound to occur in 3.32Found to occur in 3.33flutter/packages/flutter repository. See also f: labels.The issue has been confirmed reproducible and is ready to work onmaterial_ui package in flutter/packagesiOS applications specificallyIssue is closed as already fixed in a newer versionOwned by Design Languages teamTriaged by Design Languages teamA fix is in flight
Type
Projects
- Status
Activity
evantea commentedon Aug 5, 2025
This bug affects the "chalk" app
evantea commentedon Aug 5, 2025
The semantics are currently being announced as RadioButton and "checked" and "not-checked", closing for now to verify with our accessibility team that this is enough. I'll re-open with more clear instructions if any action is necessary :)
evantea commentedon Aug 5, 2025
Re-opening! The information provided above is only happening on Android, for iOS it simply says the following no matter the state of the buttons:
tirth-patel-nc commentedon Aug 6, 2025
@evantea, thanks for the report. We are seeing the same behavior with the latest SDK versions on iOS. My colleague verified it on iOS as well:
19 remaining items
Fix platform specific semantics for time picker buttons (#176373)
Fix platform specific semantics for time picker buttons (flutter#176373)
Fix platform specific semantics for time picker buttons (flutter#176373)
github-actions commentedon Oct 17, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.Fix platform specific semantics for time picker buttons (flutter#176373)
Fix platform specific semantics for time picker buttons (#176373)
Fix platform specific semantics for time picker buttons (#176373)