-
Bug
-
Resolution: Fixed
-
Low
-
4.20.0
-
Severity 2 - Major
-
Issue Summary
No visual label is present and the purpose of this field is not clear without a visual label.
Element Name: Form label of text fields that appear on expanding the Combobox.
Location of the element: The text fields that appear on expanding the Combobox.
Issue details: These text fields that appear on expanding the Combobox are missing the form labels.
Note: Similar issue on all coombox of the page.
Tested URL
https://instenv-5971-nizh.instenv.atl-test.space/servicedesk/customer/portal/1/create/35
Steps to Reproduce
- 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 listbox widget presents a list of options and allows a user to select one or more of them. A listbox that allows a single option to be chosen is a single-select listbox; one that allows multiple options to be selected is a multi-select listbox.
Fix this issue by doing ONE of the following:
1. Use an HTML <select> element for a widget where one option is selected (a single-select listbox).
2. For a multi-select listbox, follow the ARIA listbox design pattern including expected keyboard interactions at: https://www.w3.org/TR/wai-aria-practices-1.1/#Listbox
REFERENCE:
WAI-ARIA Authoring Practices:: https://www.w3.org/TR/wai-aria-practices-1.1/#Listbox
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: 749900
Bulldog Ref: JSMDC-12716
- is blocked by
-
JSMDC-12716 You do not have permission to view this issue
- is resolved by
-
- mentioned in
-
Page Failed to load
[JSDSERVER-11653] Example Summary - Step 1 : Visible label missing.
| Fix Version/s | New: 10.0.1 [ 109016 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Status | Original: Gathering Impact [ 12072 ] | New: In Progress [ 3 ] |
| Remote Link | Original: This issue links to "A11Y-179 (Bulldog)" [ 931043 ] | New: This issue links to "A11Y-179 (JIRA Server (Bulldog))" [ 931043 ] |
| Remote Link | New: This issue links to "A11Y-179 (Bulldog)" [ 931043 ] |
| Labels | Original: 3.3.2 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-jsm ax-medium-priority ax-mid-priority ax-platform-dc ax-qa ax-qa-prioritised ax-qa-ready | New: 3.3.2 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-jsm ax-jsmdc-helpcenter ax-medium-priority ax-mid-priority ax-platform-dc ax-qa ax-qa-prioritised ax-qa-ready |
| Remote Link | New: This issue links to "Page (Confluence)" [ 911963 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Labels | Original: 3.3.2 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-jsm ax-mid-priority ax-platform-dc ax-qa ax-qa-prioritised ax-qa-ready | New: 3.3.2 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-jsm ax-medium-priority ax-mid-priority ax-platform-dc ax-qa ax-qa-prioritised ax-qa-ready |
| Labels | Original: 3.3.2 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-jsm ax-mid-priority ax-platform-dc ax-qa-prioritised ax-qa-ready | New: 3.3.2 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-jsm ax-mid-priority ax-platform-dc ax-qa ax-qa-prioritised ax-qa-ready |