Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Not a bug
    • Affects Version/s: 1.9.5
    • Fix Version/s: 2.0
    • Component/s: Accessibility
    • Labels:
      None
    • Affected Branches:
      MOODLE_19_STABLE
    • Fixed Branches:
      MOODLE_20_STABLE

      Description

      This is well-known in the Moodle development community, but it's still a very important issue: the jump menu is like quicksand for a screen reader user. The jump menu contains a list of every page in the course. Once a page is selected, the user is taken there automatically, with no further action.

      This is a problem in a common use case, observed in all screen reader users:

      1. User tabs into the control.
      2. User scrolls up and down, reading the options.
      3. User tabs out, intending to go to the next item on the page.
      4. At this point, the last page they read in the list is loaded.

      Why it matters

      Once a user focuses the control it's very difficult to exit it without switching to another page. Because this takes place without explicit action on the part of the user it is unexpected behavior, and causes frustration and confusion.

      Possible solution

      Remove or refactor the jump menu. Even a small change like removing the JavaScript which moves to a new page and replacing it with a button would be helpful. Since it's of little use to blind users, it could be made a user preference, as long as it's turned off by default.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              moodle.com moodle.com
              Reporter:
              tsala Helen Foster
              Tester:
              Nobody
              Participants:
              Component watchers:
              Adrian Greeve, Jake Dallimore, Mathew May, Mihail Geshoski, Peter Dias
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Fix Release Date:
                24/Nov/10