Details

    • Type: Sub-task
    • Status: CLOSED
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.6.0
    • Fix Version/s: 2.6.4 [tentative], 2.7.2, 2.8.0
    • Component/s: Accessibility, Assignments
    • Labels:
      None
    • Environment:
      Using Sakai with Adaptive Technologies (Screen-readers, screen-magnifiers, etc.)

      Description

      The list navigator buttons in the assignments tool use a combination of the the less than, greater than, and vertical bar/bang characters to represent First Page, Previous Page, Next Page, and Last Page. Most adaptive technologies default to verbosity settings that won't announce these characters resulting in the user simply hearing "button" and not knowing what the button's purpose is. At best, the symbols are announced (i.e.: "greater than"). Also, the select element for setting the number of items displayed in a page is not explicitly labeled.

      Each button can be wrapped with a fieldset and legend element to prepend the legend's child text as an appropriate contextual text as a label for the button. CSS can be used to hide the fieldset and legend text.

      What I'm proposing is to do is to change this:

      <form name="firstpageForm" class="inlineForm" method="post" action="#toolForm("$action")">
      <input type="submit" name="eventSubmit_doList_first" value="|<" title="$tlang.getString("uselis.first")" />
      </form>

      to this:

      <form name="firstpageForm" class="inlineForm" method="post" action="#toolForm("$action")">
      <fieldset><legend>$tlang.getString("uselis.first")</legend><input type="submit" name="eventSubmit_doList_first" value="|<" title="$tlang.getString("uselis.first")" /></fieldset>
      </form>

      The default behavior in JAWS would then be to read the legend text and then the text on the button. For screen-reader users who have set punctuation to non-speaking, they would simply hear the legend text (something like "Next 5"). Those with their screen-reader set to speak punctuation would hear "Next 5 greater than", though, which is awkward but more informative than simply "greater than". It would probably make more since if the text used for the titles included a verb. Something like: "display next 5".

      Additional CSS is needed in the tool_base.css file to prevent the default rendering of the fieldset and legend elements. I'm not familiar with Sakai's CSS naming rules – something like this would do it:

      div.listNav fieldset

      { display:inline; margin:0; padding:0; }

      div.listNav legend

      { display:inline; margin:0; padding:0; position: absolute !important; clip: rect(1px 1px 1px 1px); /* IE6, IE7 */ clip: rect(1px, 1px, 1px, 1px); }

      The unlabeled select element has a simpler fix: adding a title attribute to the select element will serve is a label.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  brichwin Brian Richwine
                  Reporter:
                  brichwin Brian Richwine
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code