You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Windows][Accessibility] Flutter widgets do not expose enabled/disabled state to windows accessibility infrastructure #184559
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.
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.
Activity
[Windows] Propagate the enabled accessibility state (flutter#184501)
Reverts "[Windows] Propagate the enabled accessibility state (flutter…
[macOS] Set static text accessibility role for read-only text fields
[macOS] Set static text accessibility role for read-only text fields
macOS: Set static text accessibility role for read-only text fields (f…
a11y: Map disabled/read-only semantics to AX node restriction
a11y: Map disabled/read-only semantics to AX node restriction
a11y: Map disabled/read-only semantics to AX node restriction
a11y: Map disabled/read-only semantics to AX node restriction (flutte…
Windows: Propagate the enabled accessibility state (reland)
Windows: Propagate the enabled accessibility state (reland)
Windows: Propagate enabled accessibility state (flutter#190507)
github-actions commentedon Aug 19, 2026
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.