Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1
    • Component/s: Accessibility
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Environment:
    • Rice Module:
      KRAD
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      In portal.do, "Main" tab/page, using JAWS INSERT+F3 (which enables the user to list the UI artifacts on the page, filtered to one type at at time, such as all headings, or all combo boxes, etc.):

      1. JAWS finds an "asdf" link on the page that isn't visible (after "Administration", and before "action list"). And it is in the tab order in forms mode (tabbing to an invisible field). And there are 3 "asdfaction listdoc search" items in the list of divisions that JAWS finds in this area. (Probably these are all related to the invisible link and tabbing to an item that isn't visible.) See also the following extract from KULRICE - 5441: 5. There is a tab stop to something that is not visible on the screen, after the "administration" tab/link is read. Seems to say "link asdf". Should be deleted. (e.g., check Check Line 151, Column 35: <a href="asdf.html">)

      2. The main tab and administration tab are recognized by JAWS as "list items", along with the 64 links on the page. The tabs should not be tagged as list items. The other UI artifacts on the page are not (e.g., "provide feedback" and "acknowledgements" links are not, "login" and "logout" buttons are not, "action list" and "doc search" buttons are not).

      3. The list of "divisions" that JAWS finds is attached (4 screen shots, summarized in a Word doc). Doesn't match UI (not sure how user uses the list of divisions - CHECK ON THIS FURTHER BEFORE ASSIGNING PRIORITY TO THIS ITEM #3).

        Attachments

          Issue Links

            Activity

            Hide
            csoders Candace Soderston (Inactive) added a comment -

            Isn't an issue for screen-reading users. They don't typically rely on div information to navigate content - more important is for the other semantic markup information to be recognized by the screen readers: headings, links, tables, form fields, etc.. These other standard screen-reading navigation aids for these are relied heavily upon.

            Show
            csoders Candace Soderston (Inactive) added a comment - Isn't an issue for screen-reading users. They don't typically rely on div information to navigate content - more important is for the other semantic markup information to be recognized by the screen readers: headings, links, tables, form fields, etc.. These other standard screen-reading navigation aids for these are relied heavily upon.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: