• Type: Sub Task Sub Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Not version specific
    • Component/s: Accessibility
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Environment:
    • Similar issues:
      KULRICE-12203Elements - Action - Validation Message needs to describe validation is “required field”
      KULRICE-5434Missing and insufficient visual indication of focus
      KULRICE-7778Required message pops up on field and not removed
      KULRICE-5422Fix confusing structure and keyboard focus order in the portal log-in screen
      KULRICE-12011KRAD Library - Elements - Label - Required Message No required indicator is shown
      KULRICE-5584Design: inline validation with Tables.
      KULRICE-10118Required fields error messages on KRAD Maint doc do not show field names
      KULRICE-7131Parameter Document - when a required field is left blank it generates an extra error message
      KULRICE-5772When field is required that uses a select control, clicking on the control to select a value gives the required error and kicks you out
      KULRICE-10618Elements -> DataTable example breaks with Uncaught TypeError when the search field is used
    • 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


      1.In many locations in KNS and KS forms, there are multiple items in a single cell that are associated with an input field: the informational text, the input field itself, a lookup control, he constraint text, etc.
      1.a. When using the down-arrows to navigate through these tables, each of these items is a focusable element (so it is difficult for a user to perceive when they've moved out of the cell to the next cell). Explore how to better associate these items together (for example, using fieldsets & legends?) so that the grouping relationship is spoken. (1.a. See item #5 in KULRICE-5437. And
      1.b. And when using the tab key to navigate, only the input field is a focusable element, as is appropriate, but insufficient information is spoken. (1.b. repair is logged in KULRICE-5422)

      2. In the focus order, when there is an asterisk to denote a field is required, the asterisk is a separate focus item rather than being a prefix added to the field's label. It would be better if it were added as a prefix to the item text, rather than be 2 separate focus stops. It sounds like they are in separate cells, so may confuse the traversal order when a user is trying to remember which column they are in.

      3. The error text is read as a list item with 3 focus stops: "List of 1 items", "Description dash", "required". Recommend we have only 1 focus element, which is a composite we build: e.g., a standard prefix we add to error strings, something like "Error on 'field label': (followed by the error text)" Only in a page level or group level summary and only if there is more than 1 error would there also be a "list of x items" line.

        Issue Links


          There are no comments yet on this issue.


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


              • Created:


                  Structure Helper Panel