Details

    • Type: Sub Task Sub Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5
    • Component/s: Accessibility
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Environment:
    • Similar issues:
      KULRICE-7773Validation links no longer jump the user to the appropriate content
      KULRICE-5437UIF Framework - Add standard markup for table semantics
      KULRICE-5423UI Framework - Add standard markup for tablist semantics - for tabs that should refresh the entire page/view contents
      KULRICE-9882Add bootstrap navbar as main portal navigation
      KULRICE-5514UI Framework - Add standard markup for Tablist semantics - for tabs that should not refresh the entire page/contents
      KULRICE-12578Weird jump behavior on Krad sample app when clicking an item
      KULRICE-7952Add support for ajax retrieval of detail content
      KULRICE-8550Uif Components (Kitchen Sink) Jump to and Focus links not working
      KULRICE-7890Links for errors do not jump correctly to the fields in question, but rather jitter and jump to the top of the page
      KULRICE-6350Visual indication of links
    • Rice Module:
      KRAD
    • Application Requirement:
      KS
    • Sprint:
      2.5.0-m2 Sprint 1, 2.5.0-m2 Sprint 3, 2.5.0-m3 Sprint 1, 2.5.0-m3 Sprint 2, 2.5.0-m4 Sprint 1, UXI 2.5.0-m4 Sprint 2, UXI 2.5.0-m5 Sprint 1, Core 2.5.0-m5 Sprint 2b
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Required for WCAG 2.0 Level A (must haves):
      – 2.4.1 - Provide a way to bypass blocks of content that are repeated on multiple pages.

      On all pages (including the portal):
      Missing a skip-to-main-content link. Provide an invisible link that comes right after the Kuali portal branding in the HTML, with alt text="Jump to main content" so that on all Kuali pages the non-sighted user doesn't have to listen to all the header information that is common on all pages before hearing the content of the page. See example snippet below. See http://webaim.org/techniques/skipnav/#invisible

      Currently, the branding for the page name is spoken first "Kuali portal index", the link "Provide Feedback" is spoken next, then the greyed out text "Rice sample app ....." (reads long string). Then the Main Menu and Administration tabs are spoken, then the action list and doc search buttons, then the logged-in user info, the entry field, and the login and logout buttons. Then the focus moves into the page content area. This is very slow for non-sighted users - the standard is to include an invisible link (positioned off-screen) to skip to the main content.

      Code snippet example follows.
      HTML:
      <div id="accessibility" class="offScreen">
      <a href="#nav">Jump to Navigation</a> |
      <a href="#main-content">Jump to Main Content</a>
      </div>

      CSS:
      .offScreen

      { position:absolute; left:-10000px; top:auto; width:1px; height:1px; overflow:hidden; }

      class="offScreen"

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Brian Smith (Inactive)
              Reporter:
              Candace Soderston (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 hour, 15 minutes
                1h 15m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 15 minutes
                1h 15m

                  Agile

                    Structure Helper Panel