Skip to content

Accessibility guideline tests should work in flutter run environment #32057

Closed

Description

@jonahwilliams

Initially because the elements we are looking for are not hitTestable, and then because we seemingly do not find the correct Rect.

cc @HansMuller

Activity

  1. added
    a: tests"flutter test", flutter_test, or one of our tests
    on May 3, 2019
  2. self-assigned this
    on May 3, 2019
  3. removed their assignment
    on Jun 9, 2020
  4. goderbauer commented on Feb 1, 2023

    @goderbauer
    Member

    @jonahwilliams Do you still have context on what was meant by this issue? Not clear to me if this is still actionable...

  5. added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Feb 1, 2023
  6. jonahwilliams commented on Feb 1, 2023

    @jonahwilliams
    ContributorAuthor

    If you have a test that makes an assertion using

    class MinimumTapTargetGuideline extends AccessibilityGuideline {
    , then that test will seemingly always fail if you use flutter run instead of flutter test

  7. removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Feb 1, 2023
  8. added
    P2Important issues not at the top of the work list
    on Feb 1, 2023
  9. added
    P3Issues that are less important to the Flutter project
    and removed
    P2Important issues not at the top of the work list
    on Jun 16, 2025
  10. chunhtai commented on Jun 16, 2025

    @chunhtai
    Contributor

    What is the use case for running guideline test in flutter run environment? lowering priority because I think most case they will be running in Flutter Tester environment

  11. changed the title [-]Accessibility guideline tests do not work with `flutter run test`[/-] [+]Accessibility guideline tests should work in flutter run environment[/+] on Nov 26, 2025
  12. chunhtai commented on Jan 15, 2026

    @chunhtai
    Contributor

    as outlined in flutter.dev/go/framework-devtool-a11y-support, we need this for future devtool accessibility tooling

  13. added
    P1High-priority issues at the top of the work list
    and removed
    P3Issues that are less important to the Flutter project
    on Jan 26, 2026
  14. self-assigned this
    on Jan 26, 2026
  15. github-actions commented on Feb 23, 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.

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

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work lista: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)a: tests"flutter test", flutter_test, or one of our testsframeworkflutter/packages/flutter repository. See also f: labels.team-frameworkOwned by Framework teamtriaged-frameworkTriaged by Framework team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions