Accessibility support for embedded Android views #19418

Activity

1. amirh

   added

   c: new featureNothing broken; request for a new capabilityNothing broken; request for a new capability

   on Jul 16, 2018
2. amirh

   assigned

   amirh

   and

   jonahwilliams

   and unassigned

   amirh

   on Jul 16, 2018
3. jonahwilliams commented on Jul 16, 2018

   

   jonahwilliams

   on Jul 16, 2018

   Contributor

   More actions

   Current plan (Android): when a native view is created, call some method on the flutter view or accessibility bridge to register the value. When the a11y tree is created on the framework side, insert a node for the native render object with some flag/id that matches the internal registry. Then either when the semantics tree is updated or when the view is inserted, match the id of the native view with the semantics node containing the special tag and send a content changed event
4. jonahwilliams

   added

   a: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)Accessibility, e.g. VoiceOver or TalkBack. (aka a11y)

   on Jul 16, 2018
5. jonahwilliams commented on Jul 16, 2018

   

   jonahwilliams

   on Jul 16, 2018

   Contributor

   More actions

   This requires a new SemanticsFlag, probably something like isExternalView. The semantics node which contained this flag could only have this flag and a label, which would be the serialized identifier used by the native view registry.
6. amirh

   added

   a: platform-viewsEmbedding Android/iOS views in Flutter appsEmbedding Android/iOS views in Flutter apps

   platform-androidAndroid applications specificallyAndroid applications specifically

   and removed

   platform-androidAndroid applications specificallyAndroid applications specifically

   on Jul 20, 2018
7. jonahwilliams commented on Aug 8, 2018

   

   jonahwilliams

   on Aug 8, 2018

   Contributor

   More actions

   Per offline discussion: It is not currently possible to determine the correct parent-child relationship for an Android view with synthetic (not based on a View hierarchy) accessibility tree, such as a web view. The nodes can be obtained, there just isn't anything we can do with them.

   There may be another API we need to provide to embedded views to communicate 1) what the full accessibility node hierarchy is and 2) when to update it/receive events.

   Reassigning to @amirh for planning.
8. jonahwilliams

   assigned

   amirh

   and unassigned

   jonahwilliams

   on Aug 8, 2018
9. zoechi

   added

   engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.

   frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.

   on Dec 6, 2018
10. 33 remaining items

    Load more

11. chinmaygarde commented on Sep 14, 2020

    

    chinmaygarde

    on Sep 14, 2020

    Contributor

    More actions

    Per Ray, this should be fixed in 1.22. That is under verification right now.
12. blasten commented on Sep 14, 2020

    

    blasten

    on Sep 14, 2020

    More actions

    This is fixed in 1.22. @bparrishMines PR should be the last step prior to closing this issue.
13. chinmaygarde commented on Sep 21, 2020

    

    chinmaygarde

    on Sep 21, 2020

    Contributor

    More actions

    Can you update the milestone of this issue please?
14. blasten

    added

    waiting for PR to land (fixed)A fix is in flightA fix is in flight

    on Sep 21, 2020
15. blasten commented on Sep 21, 2020

    

    blasten

    on Sep 21, 2020

    More actions

    @chinmaygarde added label waiting for PR to land (fixed)

    👍React with 👍1Reacted by Chinmay Garde
16. blasten

    modified the milestones: 1.22 - August 2020, 1.23 - September 2020 on Sep 21, 2020
17. blasten

    added

    P1High-priority issues at the top of the work listHigh-priority issues at the top of the work list

    and removed

    P2

    on Sep 29, 2020
18. Hixie

    modified the milestones: 1.23 - September 2020, OverdueThis milestone has been deleted on Oct 6, 2020
19. blasten commented on Oct 14, 2020

    

    blasten

    on Oct 14, 2020

    More actions

    This has been fixed in 1.22 - use hybrid composition to make an Android view fully accessible. Hybrid composition should work 100% of the times just like any other Android view inside a vanilla Android app.

    https://flutter.dev/docs/development/platform-integration/platform-views?tab=android-platform-views-kotlin-tab#hybrid-composition
20. blasten

    closed this as completedon Oct 14, 2020
21. github-actions commented on Aug 8, 2021

    

    github-actionsbot

    on Aug 8, 2021

    More 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.
22. github-actions

    locked as resolved and limited conversation to collaborators on Aug 8, 2021