• 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:
    • Environment:
    • Similar issues:
      KULRICE-10914User Preference: Open inquiries in lightbox or new browser.
      KULRICE-10913Add button/link to detach (open in new browser) inquiry lightbox
      KULRICE-10915Create a system param for opening inquiries in lightboxes or new browser window
      KULRICE-1605Clicking on a Document ID from Doc Search opens a new window (different behavior than Action List)
      KULRICE-12816If a KRAD screen is opened in multiple tabs (say 5 or more) of a browser, then the button controls and functionality does not work in the first tabs (more than 5 before the latest tab).
      KULRICE-3697When submitting new Person, browser screen continuously scrolls
      KULRICE-2006Opening KIM docs from workflow action list should not spawn new browser window
      KULRICE-7040Add info on new SuperUser's Tab to User's Guide
      KULRICE-5355Lookup - return values opens new tab, the return target is not set
      KULRICE-9053Cannot perform multiple KRAD document actions with certain browsers
    • Rice Module:
    • Application Requirement:
    • 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


      Links that will open a new browser tab or window need to convey that to the end user.

      Required for WCAG 2.0 A level (must have) criteria 2.4.4: "Link purpose (in context): the purpose of each link can be determined from the link text alone or from the link text together with its programmatically-determined link context"

      There are standard shortcuts for navigating across browser tabs and for cycling through open windows, so non-sighted users will be able to get back to the location from which they activated a link if they know that link put them on new browser tab or window.

      There are two ways we can enable this to be programmatically-determined, using standard mark-up:

      o We can convey this through prefixing in the link title, giving the link title the value of something like title = "Opens new browser tab - <additional link title string>". Or
      o We can convey it through adding an image to the link (that will also convey to sighted users that this link will open a new browser tab/window), and giving the alt text the value of something like = "Opens new browser tab - <additional alt text string>"

      Example, in the (applies as well to links in any application/form that will open a new browser tab or window):

      1. When you link to "provide feedback" or to "acknowledgements", JAWS doesn't announce that user is moving to a new browser tab. The user can get back to the Kuali hub page using the standard controls (CTRL-SHFT-TAB, the standard JAWS shortcut to switch to the previous browser tab), but would not know that it is still open on another browser tab. Example, link title or alt text on an image added to these links could be something like "Opens new browser tab - <Provide Feedback>"

      (also, links should not have heading tags - see KULRICE-5692)

        Issue Links


          There are no comments yet on this issue.


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


              • Created:

                Time Tracking

                Original Estimate - 2 hours
                Remaining Estimate - 0 minutes
                Time Spent - 2 hours


                    Structure Helper Panel