Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-71671

Using TalkBack, moving forward when we are on the last element of a menu closes menu

XMLWordPrintable

    • MOODLE_400_STABLE
    • MOODLE_400_STABLE
    • MDL-71671-master
    • Hide

      You need TalkBack on an Android device or VoiceOver on a touch screen IOS device (like iPhone) for this test

      Test 1

      1. Log in as admin
      2. Go to the profile page and then go to the edit profile page
      3. Scroll down until you see the Atto editor for the description field
      4. Enable your screen reader (either TalkBack or VoiceOver)
      5. Open the 'Paragraph styles' menu by clicking on its button (single tap on the button and then double tap)
      6. Continue to navigate through the options (swipe right)
      7. Verify that you can move to the (B) button on the Atto editor toolbar if you continue swiping right

      Test 2

      1. Log in as admin
      2. Go to the profile page and then go to the edit profile page
      3. Scroll down until you see the Atto editor for the description field
      4. Create a table with default values
      5. Enable your screen reader (either TalkBack or VoiceOver)
      6. Enter a cell of the table
      7. Click on the table button in the toolbar again to open the table menu
      8. Continue to navigate through the options (swipe right)
      9. Verify that you can move to the 'clear formatting' button on the Atto editor toolbar if you continue swiping right

       

      Show
      You need TalkBack on an Android device or VoiceOver on a touch screen IOS device (like iPhone) for this test Test 1 Log in as admin Go to the profile page and then go to the edit profile page Scroll down until you see the Atto editor for the description field Enable your screen reader (either TalkBack or VoiceOver) Open the 'Paragraph styles' menu by clicking on its button (single tap on the button and then double tap) Continue to navigate through the options (swipe right) Verify that you can move to the (B) button on the Atto editor toolbar if you continue swiping right Test 2 Log in as admin Go to the profile page and then go to the edit profile page Scroll down until you see the Atto editor for the description field Create a table with default values Enable your screen reader (either TalkBack or VoiceOver) Enter a cell of the table Click on the table button in the toolbar again to open the table menu Continue to navigate through the options (swipe right) Verify that you can move to the 'clear formatting' button on the Atto editor toolbar if you continue swiping right  
    • 0
    • Internationals - 4.0 Sprint 1, HQ Team International Sprint 2, HQ Team International Sprint 3, HQ Team International Sprint 4, HQ Team International Sprint 5, HQ Team International Sprint 6, HQ Team International Sprint 7, HQ Team International Sprint 8

      • Replication with TalkBack in touch navigation: I activate the Font Color button (one-finger double tap). The menu opens and a script forces the focus on the first menu item. I continue to navigate through the options (swipe right). When I reach the end of the menu, the focus leaves the page and goes back to the Chrome browser interface. I swipe left again, but I can't get back to the menu. I have to put the focus back on the page and navigate back to the Atto editor (swipe right). When I get to the Font Color button again, the menu has remained open. If I swipe left again, the focus continues on the other buttons instead of entering the menu (issue 2). To avoid the issue, I would have had to activate the menu button again (one-finger double tap) to trigger the script that forces the focus on the first menu item. This is counterintuitive, as the menu is already open.

      Moreover, it is impossible to close the menu by activating the button that triggered its opening (toggle effect). However, to simulate the behavior of an application menu in an authentic way, this possibility should be offered to mouse and touch navigation users. Of course, the toggle effect of the button should not be implemented for keyboard navigation. In this case, an application menu provides for navigation restricted to the menu items and an exit with the Escape key bringing the focus back to the button. This keyboard behavior has been well implemented in Atto.

      • Application with VoiceOver in touch navigation: I activate the Font Color button (one-finger double tap). The menu opens and a script forces the focus on the first menu item. I continue to navigate through the options (swipe right). When I reach the end of the menu, the focus leaves the page and goes back to the Safari browser interface. I try to go back with a swipe left. Contrary to what happened in TalkBack, I manage to go back to the menu. However, I can't reach the button. Indeed, after leaving the menu with a swipe left, VoiceOver announces the presence of a level 3 header (H3), then the focus exits the Atto editor without having been on the button. In the StudiUM Continuing Education interface, the focus is at the bottom of the page, on the "Back to Top" link.

            rezaie9 Shamim Rezaie
            rezaie9 Shamim Rezaie
            Dongsheng Cai Dongsheng Cai
            Jun Pataleta Jun Pataleta
            Glyn (Mathew) May Glyn (Mathew) May
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days, 6 hours, 55 minutes
                2d 6h 55m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.