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

1. Turn on Voicover
2. Navigate to the DateTimePicker
3. Select a date
4. Navigate to the Clock

Expected results

TalkBack users are able to render the clock element in the reading order. It is conveyed by TB as "Select <hours/minutes>" but this is not something they can interact with and the textual information is not useful to them.

Actual results

Consider hiding the clock from TalkBack users so that it gets skipped in the reading order as they navigate linearly through the dialog.

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

Screenshots / Video demonstration

Logs

[Paste your logs here]

Flutter Doctor output

[Paste your output here]