Issue Summary

      The element is not accessible by keyboard alone and there is no conforming accessible version of the same functionality reachable from the non-conforming page.

      Name of the Element:
      The request submenu "elements:
      Example:
      -Approvals
      --My requests
      -All requests

      Location:
      Located in the header section

      Note:
      -Issue is Observed with screen reader turn on

      Tested URL

       

      Steps to Reproduce

      1. Step 1

      Actual Results

      Actual results

      Expected Results

      Fix Information
      RULE :
      The name, role, value, states, and properties of user interface components MUST be programmatically determinable by assistive technologies.

      HOW TO FIX:
      A combobox is a widget made up of the combination of two distinct elements: 1) a single-line textbox, and 2) an associated pop-up element for helping users set the value of the textbox.

      Fix this issue by using ONE of the following techniques:
      1. Use an HTML <select> element with <option> elements to create the drop-down menu.
      2. Use the ARIA design pattern for a combobox. View the full ARIA design pattern for a combo including expected keyboard interactions and examples: https://www.w3.org/TR/wai-aria-practices-1.1/#combobox

      REFERENCE:
      W3C HTML5 Recommendation: https://www.w3.org/TR/html5/sec-forms.html#the-select-element
      WAI-ARIA Authoring Practices: https://www.w3.org/TR/wai-aria-practices-1.1/#combobox

      BACKGROUND:
      Every user interface control must have a role along with any applicable states and properties so that screen reader users know how to interact with the control. Native HTML elements - such as <button>, <a>, <input>, <select> - already have a role, and their necessary states and properties - such as the checked/unchecked state of a checkbox - are automatically conveyed so nothing more needs to be done. If you create a custom version of a native HTML element or a custom control or widget that does not have a native HTML equivalent, you must add the relevant role(s) and any applicable states and properties using ARIA as well as expected keyboard interactions.

      Screenshot

      Screen Recording

      screen recording

      Workaround

      workaround

      Bug Ref: 750105

      Bulldog Ref:

          Form Name

            [JSDSERVER-12074] Header : Inaccessible by keyboard and no conforming alternate.

            There are no comments yet on this issue.

              a955dc6cda19 Oleksandr Stoliar
              12b69dcabe29 Matthew Brennan
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: