Navigate to Partition field

Oct 13, 2025 by sorusgentrification.com 122 views

Introduction

As we strive to create a more inclusive and accessible experience for users with disabilities, it is essential to ensure that our applications comply with the Web Content Accessibility Guidelines (WCAG 2.2). In this article, we will explore the issues with options in the lists on the Analytics: Discover page, specifically when using assistive technology like screen readers. We will delve into the preconditions, steps to reproduce the issue, actual and expected results, and provide a meta issue summary.

Preconditions

To reproduce the issue, follow these preconditions:

Navigate to the Analytics page
Ensure you are using the Discover page
Use a screen reader, specifically NVDA (NonVisual Desktop Access)

Steps to Reproduce

To reproduce the issue, follow these steps:

Navigate to Patterns tab: Open the Analytics page and navigate to the Patterns tab.
Navigate to Create anomaly detection job... and press Enter: Press the Enter key to open the Create anomaly detection job dialog.
Turn on Enable per-partition categorization switch: Toggle the Enable per-partition categorization switch to enable it.
Navigate to Partition field: Navigate to the Partition field in the dialog.
Navigate through options in the opened dialog: Use the arrow keys or other navigation methods to browse through the options in the dialog.
Observe page and screen reader: Observe the page and the screen reader's output to identify the issue.

UI Elements + NVDA Speech Viewer

The following image illustrates the UI elements and NVDA Speech Viewer:

Actual Result

When reproducing the issue, you may observe the following:

Different total numbers of options are announced with existing options (e.g., "...1 of 9", "...8 of 10").
Additional text is announced for options without a total number.

Expected Result

The expected result is:

Correct total numbers are announced with each existing option.
No additional text is announced for options without a total number.

Meta Issue

The meta issue summary is as follows:

Kibana Version: 8.18.0-SNAPSHOT
OS: Windows 11 Pro
Browser: Chrome Version 131.0.6778.140 (Official Build) (64-bit)
Screen reader: NVDA
WCAG or Vendor Guidance (optional):
- Understanding SC 4.1.2: Name, Role, Value (Level A) (https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html)
- Understanding SC 1.3.1: Info and Relationships (Level A) (https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html)

Related Issues

This issue is related to the following GitHub issue:

https://github.com/elastic/kibana-team/issues/1559

Conclusion

In conclusion, the Analytics: Discover page issues with options in the lists are a significant concern for users with disabilities. By following the preconditions, steps to reproduce, and observing the UI elements and NVDA Speech Viewer, we can identify the issue and work towards a solution. The expected result is to announce correct total numbers with each existing option and no additional text for options without a total number. By addressing this issue, we can improve the accessibility and inclusivity of our application.

Recommendations

To resolve this issue, we recommend the following:

Review the code and ensure that the total numbers are correctly announced for each option.
Test the application with assistive technology, such as screen readers, to identify any issues.
Update the code to announce correct total numbers with each existing option and no additional text for options without a total number.
Verify that the updated code meets the WCAG 2.2 guidelines and vendor guidance.

Introduction

In our previous article, we explored the issues with options in the lists on the Analytics: Discover page, specifically when using assistive technology like screen readers. We delved into the preconditions, steps to reproduce the issue, actual and expected results, and provided a meta issue summary. In this article, we will answer some frequently asked questions (FAQs) related to this issue.

Q: What is the issue with options in the lists on the Analytics: Discover page?

A: The issue is that different total numbers of options are announced with existing options, and additional text is announced for options without a total number. This makes it difficult for users with disabilities to navigate the page using assistive technology.

Q: What are the preconditions for reproducing the issue?

A: To reproduce the issue, you need to navigate to the Analytics page, ensure you are using the Discover page, and use a screen reader, specifically NVDA (NonVisual Desktop Access).

Q: What are the steps to reproduce the issue?

A: The steps to reproduce the issue are:

Navigate to the Patterns tab.
Navigate to Create anomaly detection job... and press Enter.
Turn on Enable per-partition categorization switch.
Navigate to Partition field.
Navigate through options in the opened dialog.
Observe page and screen reader.

Q: What is the expected result?

A: The expected result is that correct total numbers are announced with each existing option, and no additional text is announced for options without a total number.

Q: What are the related issues?

A: This issue is related to the following GitHub issue:

https://github.com/elastic/kibana-team/issues/1559

Q: What are the WCAG or Vendor Guidance (optional) related to this issue?

A: The WCAG or Vendor Guidance (optional) related to this issue are:

Understanding SC 4.1.2: Name, Role, Value (Level A) (https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html)
Understanding SC 1.3.1: Info and Relationships (Level A) (https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html)

Q: How can I help resolve this issue?

A: You can help resolve this issue by:

Reviewing the code and ensuring that the total numbers are correctly announced for each option.
Testing the application with assistive technology, such as screen readers, to identify any issues.
Updating the code to announce correct total numbers with each existing option and no additional text for options without a total number.
Verifying that the updated code meets the WCAG 2.2 guidelines and vendor guidance.

Conclusion

In conclusion, the Analytics: Discover page issues with options in the lists are a significant concern for users with disabilities. By understanding the issue, preconditions, steps to reproduce, and expected results, we can work towards a solution. We hope this Q&A article has provided valuable information and insights to help resolve this issue.

Recommendations

To resolve this issue, we recommend the following:

Review the code and ensure that the total numbers are correctly announced for each option.
Test the application with assistive technology, such as screen readers, to identify any issues.
Update the code to announce correct total numbers with each existing option and no additional text for options without a total number.
Verify that the updated code meets the WCAG 2.2 guidelines and vendor guidance.

By following these recommendations, we can improve the accessibility and inclusivity of our application and provide a better experience for users with disabilities.