Skip to content

[Windows][Accessibility] Flutter widgets do not expose enabled/disabled state to windows accessibility infrastructure #184559

Closed

Description

Steps to reproduce

Add a Flutter button with onPressed valued (like in demo application)
Add a Flutter button with onPressed: null
Run the application
Inspect accessibility features of the buttons (for example using FlaUInspect or Appium Inspector)

Expected results

The enabled/disabled state is propagated to Windows accessibility infrastructure.

Actual results

The enabled/disabled state is not propagated to Windows accessibility infrastructure.

Code sample

Code sample
      FloatingActionButton(
        onPressed: _incrementCounter,
        child: const Icon(Icons.add),
      ),
      FloatingActionButton(
        onPressed: null,
        child: const Icon(Icons.add),
      ),

Screenshots or Video

Screenshots / Video demonstration

[Upload media here]

Logs

Logs
[Paste your logs here]

Flutter Doctor output

Doctor output
[Paste your output here]

Activity

  1. added
    a: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)
    fyi-windowsFor the attention of the Windows platform team
    team-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)
    platform-windowsBuilding on or for Windows specifically
    team-windowsOwned by the Windows platform team
    fyi-accessibilityFor the attention of Framework Accessibility team
    P2Important issues not at the top of the work list
    triaged-windowsTriaged by the Windows platform team
    and removed
    team-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)
    fyi-windowsFor the attention of the Windows platform team
    on Apr 3, 2026
  2. added a commit that references this issue on Aug 5, 2026
    8eef451
  3. github-actions commented on Aug 19, 2026

    @github-actions

    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 -v and a minimal reproduction of the issue.

  4. locked as resolved and limited conversation to collaborators on Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work lista: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)a: desktopRunning on desktopplatform-windowsBuilding on or for Windows specificallyteam-windowsOwned by the Windows platform teamtriaged-windowsTriaged by the Windows platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions