Skip to content

[Search:Indices:Pipelines page] Unclear interaction with checkable cards in the Pipeline settings dialog #196663

@L1nBra

Description

@L1nBra

Description
Certain elements, in this case checkboxes (checkable cards), should behave expectedly. The user should be able to check or uncheck any card. Also, user should understand which checkbox is mandatory and the state of them should not change automatically. In case they should change automatically, user should be aware that it can happen and why.

Preconditions
Stateful Indices -> Pipelines page is opened.
Use Screen Reader (NVDA).

Steps to reproduce

1.Navigate to Settings button while using only keyboard by pressing Tab key in Ingest Pipelines section.
2.Press Enter.
3.Navigate to checkable cards.
4.Uncheck first two cards and check the last card while navigating to the card and pressing Space bar.
5.Observe the cards.
6.Observe screen reader announcement.

Gif showing issue
Image

NVDA Speech Viewer
Image

Actual Result

  • First two cards gets unchecked, but soon automatically they are checked again. The last card, after checking it, automatically gets unchecked. Screen reader announces correctly the card's state, then "not checked", "checked" for one card (same with others).
    No indication, information present which cards are mandatory.

Expected Result

  • It is possible to check or uncheck any card and it automatically doesn't get checked, screen reader doesn't announce change of the state which happened automatically (because the change automatically shouldn't happen).
    In case any card is mandatory it is marked as mandatory, or if they are only for reference only - they should be visible for the user, but he/she should not even be able to check them, only hear the information that they are only for representation purpose and short description.

Meta Issue

Kibana Version: 8.16.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 129.0.6668.101 (Official Build) (64-bit)

Screen reader: NVDA

WCAG or Vendor Guidance (optional)

Related to: https://github.com/elastic/search-team/issues/8256

Metadata

Metadata

Labels

Project:AccessibilityTeam:SearchWCAG Adefect-level-3Moderate UX disruption or potentially confusing a11yimpact:highAddressing this issue will have a high level of impact on the quality/strength of our product.loe:mediumMedium Level of Effortsdh-driven

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions