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

Skip to content

MacOS accessibility live region does not work #167318

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

Open
ash2moon opened this issue Apr 16, 2025 · 1 comment
Open

MacOS accessibility live region does not work #167318

ash2moon opened this issue Apr 16, 2025 · 1 comment
Labels
a: accessibility Accessibility, e.g. VoiceOver or TalkBack. (aka a11y) fyi-macos For the attention of macOS platform team P2 Important issues not at the top of the work list team-accessibility Owned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter) triaged-accessibility Triaged by Framework Accessibility team

Comments

@ash2moon
Copy link
Contributor

ash2moon commented Apr 16, 2025

Steps to reproduce

  1. Run the code sample in MacOS
  2. Turn on accessibility voice over
  3. Click the + sign to add a new number to the live region counter.

Expected results

Should announce the new numbers as it is incremented. This works fine on Android and Chrome.

Actual results

Does not announce anything.

Code sample

Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Live Region Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // TRY THIS: Try running your application with "flutter run". You'll see
        // the application has a purple toolbar. Then, without quitting the app,
        // try changing the seedColor in the colorScheme below to Colors.green
        // and then invoke "hot reload" (save your changes or press the "hot
        // reload" button in a Flutter-supported IDE, or press "r" if you used
        // the command line to start the app).
        //
        // Notice that the counter didn't reset back to zero; the application
        // state is not lost during the reload. To reset the state, use hot
        // restart instead.
        //
        // This works for code too, not just values: Most code changes can be
        // tested with just a hot reload.
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Live Region Demo'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // TRY THIS: Try changing the color here to a specific color (to
        // Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
        // change color while the other colors stay the same.
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          //
          // TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
          // action in the IDE, or press "p" in the console), to see the
          // wireframe for each widget.
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Semantics(
              liveRegion: true,
              child: Text(
                '$_counter',
                style: Theme.of(context).textTheme.headlineMedium,
              ),
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration

[Upload media here]

Logs

No response

Flutter Doctor output

Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel [user-branch], 3.32.0-1.0.pre.83, on macOS 15.3.2 24D81 darwin-arm64, locale en)
    ! Flutter version 3.32.0-1.0.pre.83 on channel [user-branch] at /Users/muhatashim/StudioProjects/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
    ! Upstream repository https://github.com/ash2moon/flutter.git is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to https://github.com/ash2moon/flutter.git to dismiss this error.
[✓] Android toolchain - develop for Android devices (Android SDK version 36.0.0-rc4)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2024.3.3)
[✓] VS Code (version 1.98.1)
[✓] Connected device (4 available)
[✓] Network resources
@ash2moon ash2moon added a: accessibility Accessibility, e.g. VoiceOver or TalkBack. (aka a11y) fyi-macos For the attention of macOS platform team P2 Important issues not at the top of the work list labels Apr 16, 2025
@darshankawar darshankawar added the team-accessibility Owned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter) label Apr 17, 2025
@chunhtai chunhtai added the triaged-accessibility Triaged by Framework Accessibility team label Apr 30, 2025
@chunhtai
Copy link
Contributor

We do have logic around live region in macos, may need to see why it is not hooked up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a: accessibility Accessibility, e.g. VoiceOver or TalkBack. (aka a11y) fyi-macos For the attention of macOS platform team P2 Important issues not at the top of the work list team-accessibility Owned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter) triaged-accessibility Triaged by Framework Accessibility team
Projects
None yet
Development

No branches or pull requests

3 participants