Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-36138

Accessibility: Multiple Choice Questions in Samigo Are Not Very Accessible

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.7.2, 2.8.0, 2.9.0
    • Fix Version/s: 2.9.1
    • Environment:
      Adaptive Tech / Non-mouse users / Screen-reader users
    • Previous Issue Keys:
      SAM-1295

      Description

      The questions delivered by deliverMultipleChoiceSingleCorrect.jsp and deliverMultipleChoiceMultipleCorrect.jsp have many keyboard accessibility issues and are not labeled appropriately for adaptive technologies.

      A video demonstrating the keyboard accessibility issues can be found here: http://screencast.com/t/di6aofsmi

      The radio buttons are not being generated as a group using the selectOnRadio and selectItems tags since the feedback right/wrong graphics and feedback comments are being woven in between the radio buttons. The existing technique forces the radio buttons to each have a unique name instead of each radio button in the group sharing the same name. This causes several problems.

      First, adaptive technology announces each radio button as being "radio button one of one" instead of "radio button 1 of 4", "radio button 2 of 4", etc. (assuming 4 buttons in the group). This keeps non-visual users from easily knowing how many answer choices are present for the question.

      Second, the text for the answer options are not explicitly associated with the radio buttons. With the arrangement of the answer text relative to the input elements complicated by the nested tables, so adaptive technologies could confuse which text goes with which input and mislead the user. The JAWS screen-reading software doesn't see the buttons as labeled and does not announce them as such (see mcscButtonsNotAffectivelyLabeled.png attached).

      Third, since the radio buttons aren't coded as a group, the standard keyboard navigation techniques aren't available. Also, the javascript code used to emulate a group of radio buttons for mouse users wasn't developed with keyboard users in mind and makes proper selection of the desired radio button by the keyboard impossible for some users.

        Gliffy Diagrams

          Attachments

          1. mcscButtonsNotAffectivelyLabeled.png
            mcscButtonsNotAffectivelyLabeled.png
            134 kB
          2. sam_1295_2.png
            sam_1295_2.png
            115 kB
          3. sam_1295.png
            sam_1295.png
            71 kB
          4. SAM-1295.diff
            9 kB
          5. SAM-1295b.diff
            4 kB
          6. test.html
            0.8 kB

            Issue Links

              Activity

                People

                • Assignee:
                  samigoteam SAMIGO TEAM (Inactive)
                  Reporter:
                  brichwin Brian Richwine
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code