Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-100545

Nested QML items with Accessible properties set does not work on Android

XMLWordPrintable

    • Android
    • b99fdae5f5 (qt/qtbase/dev) b99fdae5f5 (qt/tqtc-qtbase/dev) f256aeb293 (qt/tqtc-qtbase/5.15) 0090e34942 (qt/qtbase/6.3) 0090e34942 (qt/tqtc-qtbase/6.3) 2f0f459c4a (qt/qtbase/6.2) 2f0f459c4a (qt/tqtc-qtbase/6.2)
    • Team One Foundation Sprint 51

      Nested QML items with accessibility info within another item with accessibility info does not show up in the accessibility hierarchy on Android.

      See the output of Appium Inspector for a failing case below:

      If the `Accessible.name` is removed from the nesting/parent element, the nested/child accessibility element `rect_inside_center` shows up in the Appium Inspector:

      There is a minimal reproducer in the attached zip archive: NestedAccessibleItemsIssue.zip

       

      An educated guess is that this was introduced in this commit:
      https://codereview.qt-project.org/c/qt/qtbase/+/325940 

      See the removal of addChild calls at line 339 here:
      https://codereview.qt-project.org/c/qt/qtbase/+/325940/3/src/android/jar/src/org/qtproject/qt5/android/accessibility/QtAccessibilityDelegate.java#b339

      (I have not tried to reintroduce the addChild code and compile Qt, so this is speculation.)

      On iOS this is not an issue. (Tested.)

        1. image-2022-02-08-17-04-20-600.png
          69 kB
          Ivan Solovev
        2. NestedAccessibleItemsIssue.zip
          5 kB
          Tom Nœrland
        3. rect_inside_center_not_showing_up.png
          257 kB
          Tom Nœrland
        4. rect_inside_center_showing_up.png
          258 kB
          Tom Nœrland
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            ivan.solovev Ivan Solovev
            tomana Tom Nœrland
            Vladimir Minenko Vladimir Minenko
            Alex Blasche Alex Blasche
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: