-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
4.22.2
-
Severity 2 - Major
-
Issue Summary
The Options button for the available IQL search results section has a missing label/descriptive text.
Tested URL
Steps to Reproduce
- Launch the URL
- In the header section Navigate to "Insights" and activate the link.
- Select the "Search objects" link from the insights menu.
- In the IQL search section, keeping the screen reader on, Add a search query.
- Navigate to the "Search" button and activate it.
- A result will appear in the main content area, navigate to the result section.
- In the available table row navigate to the actions button at the end of the row.
Actual Results
On the "Search Objects" page, the "Actions" button for the IQL query result in the main content area table does not have a label or a descriptive text associated with it. Hence the assistive technology users will be unable to identify the purpose of this button.
Expected Results
Add a descriptive label for the menu button via the aria-label attribute. For example, provide the label “Actions”. This will help to make the purpose of form controls meaningful for screen reader users.
Additionally, the button is only available on mouse hover and not on keyboard focus. This will make it the keyboard only users difficult to access the functionality.
Screenshot
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available.
Bug Ref: 745878
Bulldog Ref:
- is duplicated by
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-11491] Filter Results/Search using a query : The Options button for IQL query results has missing label/descriptive text
| Labels | Original: 4.1.2 Accessibility Level-A WCAG21 ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jsm ax-platform-dc ax-qa ax-qa-prioritised ax-vpat-critical sprint1 | New: 4.1.2 Accessibility Level-A WCAG21 ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-critical ax-critical-priority ax-dev-ready ax-high-priority ax-jsm ax-platform-dc ax-qa ax-qa-prioritised ax-vpat-critical sprint1 |
| Labels | Original: 4.1.2 Accessibility Level-A WCAG21 ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jsm ax-platform-dc ax-qa-prioritised ax-vpat-critical sprint1 | New: 4.1.2 Accessibility Level-A WCAG21 ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jsm ax-platform-dc ax-qa ax-qa-prioritised ax-vpat-critical sprint1 |
| Labels | Original: 4.1.2 Accessibility Level-A WCAG21 ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jsm ax-platform-dc ax-qa-prioritised ax-vpat-critical | New: 4.1.2 Accessibility Level-A WCAG21 ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jsm ax-platform-dc ax-qa-prioritised ax-vpat-critical sprint1 |
| Sprint | New: JSM Sprint 1 [ 6985 ] | |
| Story Points | New: 1 |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Status | Original: Ready for Development [ 10049 ] | New: In Progress [ 3 ] |
| Link |
New:
This issue is duplicated by |
| Assignee | New: Olena Lymar [ aee694511cd1 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Ready for Development [ 10049 ] |
| Description |
Original:
h3. Issue Summary
The Options button for the available IQL search results section has a missing label/descriptive text. h3. Tested URL [https://instenv-19536-ipiz.instenv.internal.atlassian.com/secure/insight/search?criteria=Name%20%3D%20xyz&schema=3] h3. Steps to Reproduce # Launch the URL # In the header section Navigate to "Insights" and activate the link. # Select the "Search objects" link from the insights menu. # In the IQL search section, keeping the screen reader on, Add a search query. # Navigate to the "Search" button and activate it. h3. Actual Results On the "Search Objects" page, the "IQL search " button for the IQL query input field in the Search header section does not have a label or a descriptive text associated with it. Hence the assistive technology users will be unable to identify the purpose of this button. h3. Expected Results Add a descriptive label for the menu button via the aria-label attribute. For example, provide the label “IQL Search”. This will help to make the purpose of form controls meaningful for screen reader users. h3. Screenshot h3. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available. Bug Ref: 745878 Bulldog Ref: |
New:
h3. Issue Summary
The Options button for the available IQL search results section has a missing label/descriptive text. h3. Tested URL [https://instenv-19536-ipiz.instenv.internal.atlassian.com/secure/insight/search?criteria=Name%20%3D%20xyz&schema=3] h3. Steps to Reproduce # Launch the URL # In the header section Navigate to "Insights" and activate the link. # Select the "Search objects" link from the insights menu. # In the IQL search section, keeping the screen reader on, Add a search query. # Navigate to the "Search" button and activate it. # A result will appear in the main content area, navigate to the result section. # In the available table row navigate to the actions button at the end of the row. h3. Actual Results On the "Search Objects" page, the "Actions" button for the IQL query result in the main content area table does not have a label or a descriptive text associated with it. Hence the assistive technology users will be unable to identify the purpose of this button. h3. Expected Results Add a descriptive label for the menu button via the aria-label attribute. For example, provide the label “Actions”. This will help to make the purpose of form controls meaningful for screen reader users. Additionally, the button is only available on mouse hover and not on keyboard focus. This will make it the keyboard only users difficult to access the functionality. h3. Screenshot !Screenshot 2022-05-24 at 12.21.09 PM.png|thumbnail! h3. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available. Bug Ref: 745878 Bulldog Ref: |