Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-7478

Keyboard focus order in checkbox groups and radiogroups

    Details

    • Similar issues:
      KULRICE-5422Fix confusing structure and keyboard focus order in the portal log-in screen
      KULRICE-5434Missing and insufficient visual indication of focus
      KULRICE-5182Add property to AttributeField that allows removing the field from the keyboard tab order
      KULRICE-7158Validation messaging - single checkbox tooltip persists/open
      KULRICE-5511# focus elements in designating required fields and in error messages
      KULRICE-5441Focus order & clean-up needed in Kuali portal header (inherited by all KNS & KS pages)
      KULRICE-5888Date picker not accessible by keyboard
      KULRICE-10816Prepare Data Dictionary Gap Analysis for Focus Group
      KULRICE-10817Prepare Transactional Gap Analysis for Focus Group
      KULRICE-7871Checkbox and Radio Group ids are not correct
    • Epic Link:
    • Rice Module:
      KRAD
    • Application Requirement:
      KS
    • Sprint:
      2.5.0-m2 Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      The keyboard focus order within checkbox groups and radiogroups should be same, regarding the tab key behavior – the group itself should be in the tab key's tab order but each option in the group should not be.
      For example, see the Rice test drive, KRAD tab, Screen element testing, Validation Framework demo (but not unique to this demo).

      Current behavior:

      • When on a field that precedes a checkbox or radiogroup, the tab key currently does get the user into the group (to the first option).
      • The arrow keys do correctly navigate across the options within the group.
      • But the tab key currently also navigates across the options within the group, instead of taking the user to the field/control that follows the checkbox or radiogroup.

        Issue Links

          Activity

          Hide
          Jessica Coltrin (Inactive) added a comment -

          moving non-blocker and non-critical m4 Jiras to 2.2-backlog

          Show
          Jessica Coltrin (Inactive) added a comment - moving non-blocker and non-critical m4 Jiras to 2.2-backlog

            People

            • Assignee:
              Tadas Paegle (Inactive)
              Reporter:
              William Washington (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Agile

                    Structure Helper Panel