Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Stateful:Indices:Pipelines page] Confusing announcement after activating JSON configurations tab #196737

Closed
L1nBra opened this issue Oct 17, 2024 · 2 comments
Assignees
Labels
defect-level-3 Moderate UX disruption or potentially confusing impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Project:Accessibility Team:Search WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Oct 17, 2024

Description
When activating a tab, information about it should be announced. Additional information which belongs to another element should not be announced in order not to confuse users, especially the ones using assistive technology.

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

Steps to reproduce

1.Navigate to JSON configurations tab while using only keyboard by pressing Tab key.
2.Press Enter.
3.Observe screen reader announcement.

NVDA Speech Viewer + UI elements
Image

Actual Result

  • Focus is on JSON configurations tab, it is announced as selected and then "test 2 of 4" is announced.

Expected Result

  • "test 2 of 4" is not announced.

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-accessibility (Project:Accessibility)

@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 17, 2024
@L1nBra L1nBra added WCAG A Team:Search defect-level-3 Moderate UX disruption or potentially confusing labels Oct 17, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 17, 2024
@L1nBra L1nBra added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Oct 30, 2024
@alexwizp alexwizp self-assigned this Nov 5, 2024
@alexwizp
Copy link
Contributor

alexwizp commented Nov 6, 2024

@L1nBra issue was already fixed. Please feel free to reopen in case if it's not true

Image

@alexwizp alexwizp closed this as completed Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect-level-3 Moderate UX disruption or potentially confusing impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Project:Accessibility Team:Search WCAG A
Projects
None yet
Development

No branches or pull requests

3 participants