-
Bug
-
Resolution: Fixed
-
Low
-
4.22.3
-
Severity 2 - Major
-
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.
Tested URL
Steps to Reproduce
- Launch the URL
- In the Insights menu, select any object schema.
- In the main content area, use keyboard tab functionality to reach "Object Graph".
- Observe that when we use the tab functionality again it skips the "Print" and "QR code" elements and directly goes to the "Stop Watching" button.
Actual Results
In the main content area, the elements such as "Print" and "QR code" do not have keyboard support. When the keyboard-only users or screen reader users navigates the webpage with the help of the keyboard, the elements get skipped after "Object Graph" and it directly goes to the Stop Watching" button. The "Print" and "QR code" elements are active with the mouse click. This will make it the keyboard-only users difficult to use this feature.
Expected Results
The interactive element such as “Print” and “QR code” must be coded as native <button> elements so that the appropriate role of the button will be announced for screen reader users on focus and they will also receive keyboard focus in tab traversal. As a workaround (not recommended), the <span> element can be provided with role=” button” and tabindex=”0”.
In addition, the button should be provided with an “aria-expanded” property and its value should be toggled programmatically to true when the content is displayed else false at other times.
Screenshot
Screen Recording
Screen Recording 2022-05-31 at 2.14.17 PM.mov
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available.
Bug Ref: 748637
Bulldog Ref: JSMDC-12821
- is resolved by
-
-
- Closed
-
- is blocked by
-
JSMDC-12821 You do not have permission to view this issue
[JSDSERVER-11609] Business Services/Create Objects : Interactive element is Inaccessible by keyboard and no conforming alternative.
| Labels | Original: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa ax-qa-prioritised ax-qa-verified ax-vpat-critical | New: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-critical ax-critical-priority ax-dev-done ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa ax-qa-prioritised ax-qa-verified ax-vpat-critical |
| Labels | Original: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa-prioritised ax-qa-verified ax-vpat-critical | New: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa ax-qa-prioritised ax-qa-verified ax-vpat-critical |
| Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 5.2.0 [ 102196 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Labels | Original: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa-prioritised ax-vpat-critical | New: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa-prioritised ax-qa-verified ax-vpat-critical |
| Labels | Original: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-dev-ready ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa-prioritised ax-vpat-critical | New: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa-prioritised ax-vpat-critical |
| Link |
New:
This issue is resolved by |
| Labels | Original: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-ready ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa-prioritised ax-vpat-critical | New: 2.1.1 Accessibility Level-A WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-dev-ready ax-high-priority ax-jsm ax-kb-user ax-platform-dc ax-qa-prioritised ax-vpat-critical |
| Description |
Original:
h3. 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. h3. Tested URL [https://instenv-21072-japp.instenv.internal.atlassian.com/secure/ObjectSchema.jspa?id=3&typeId=43&mode=object&objectId=201] h3. Steps to Reproduce # Launch the URL # In the Insights menu, select any object schema. # In the main content area, use keyboard tab functionality to reach "Object Graph". # Observe that when we use the tab functionality again it skips the "Print" and "QR code" elements and directly goes to the "Stop Watching" button. h3. Actual Results In the main content area, the elements such as "Print" and "QR code" does not have keyboard support. When the keyboard-only users or screen reader users navigates the webpage with the help of the keyboard, the elements get skipped after "Object Graph" and it directly goes to the Stop Watching" button. This will make it the users difficult to use this feature. h3. Expected Results The interactive element such as “Print” and “QR code” must be coded as native <button> elements so that the appropriate role of the button will be announced for screen reader users on focus and they will also receive keyboard focus in tab traversal. As a workaround (not recommended), the <span> element can be provided with role=” button” and tabindex=”0”. In addition, the button should be provided with an “aria-expanded” property and its value should be toggled programmatically to true when the content is displayed else false at other times. h3. Screenshot !https://axeauditor.dequecloud.com/api/v1/file/62572848-6659-11ec-a07c-af7fb52b8823|width=589,height=316! h3. Screen Recording [^Screen Recording 2022-05-31 at 2.14.17 PM.mov] h3. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available. Bug Ref: 748637 Bulldog Ref: JSMDC-12821 |
New:
h3. 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. h3. Tested URL [https://instenv-21072-japp.instenv.internal.atlassian.com/secure/ObjectSchema.jspa?id=3&typeId=43&mode=object&objectId=201] h3. Steps to Reproduce # Launch the URL # In the Insights menu, select any object schema. # In the main content area, use keyboard tab functionality to reach "Object Graph". # Observe that when we use the tab functionality again it skips the "Print" and "QR code" elements and directly goes to the "Stop Watching" button. h3. Actual Results In the main content area, the elements such as "Print" and "QR code" do not have keyboard support. When the keyboard-only users or screen reader users navigates the webpage with the help of the keyboard, the elements get skipped after "Object Graph" and it directly goes to the Stop Watching" button. The "Print" and "QR code" elements are active with the mouse click. This will make it the keyboard-only users difficult to use this feature. h3. Expected Results The interactive element such as “Print” and “QR code” must be coded as native <button> elements so that the appropriate role of the button will be announced for screen reader users on focus and they will also receive keyboard focus in tab traversal. As a workaround (not recommended), the <span> element can be provided with role=” button” and tabindex=”0”. In addition, the button should be provided with an “aria-expanded” property and its value should be toggled programmatically to true when the content is displayed else false at other times. h3. Screenshot !https://axeauditor.dequecloud.com/api/v1/file/62572848-6659-11ec-a07c-af7fb52b8823|width=589,height=316! h3. Screen Recording [^Screen Recording 2022-05-31 at 2.14.17 PM.mov] h3. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available. Bug Ref: 748637 Bulldog Ref: JSMDC-12821 |