Details

    • Type: Sub Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: Not version specific
    • Component/s: Accessibility
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Environment:
    • 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

      Related to WCAG 2.0 Level A (must have) criteria 4.1.1 Parsing: in content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, & IDs are unique (except where specs allow these features)

      In portal.do:
      1. Too many H1s in Kuali portal. There should be only 1 per page. Also check for empty H1s and eliminate them. Also check to make sure links to other pages are not coded as H1s (links cannot contain heading elements, they can contain titles). See also items 2, 3 & 4 in KULRICE-5441, related to too many H1s - e.g., "provide feedback" link is an H1 - eliminate the heading tag from that link. See also KULRICE-5673, 5423 & 5692.

      2. The text/sub-headings under the H2 sections in portal.do are missing heading tags, so they don't get listed in the headings list. E.g., "Screen Element Testing" and "BO Class Tests". Need H3 tags. They do get read and don't need focus, but this is not great UX. Adding H3 tags would make it possible for users to move to the H3 sections in exploring the page and the items in these sections, in this way (e.g., down-arrow to or enter "3" to get to "Maintenance Docs"). For a sighted person, we've grouped these things so the user can first visually browse the larger categories before zooming their attention down into one. Same should be true for non-sighted persons - they may want to get a sense of the conceptual groupings and then explore the links in each subsection, rather than get a very LONG-list reading of the entire page of links by JAWS. (For example, bring up the headings list in JAWS to use that as a jumping off point.)

      Recommendation: Add H3 tags to the text strings that don't have any heading tags and that are nested under the H2 sections.

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: