Skip to content

[Observability:Synthetics:Settings]Different name announced than the one present for element #221352

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.

Sign up for GitHub

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

Jump to bottom
Open
L1nBra opened this issue May 23, 2025 · 1 comment
Open

[Observability:Synthetics:Settings]Different name announced than the one present for element #221352

L1nBra opened this issue May 23, 2025 · 1 comment
Labels
defect-level-2 Serious UX disruption with workaround impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. needs-team Issues missing a team label obs-accessibilty A11Y issues in the Obs. solution. Project:Accessibility WCAG A

Comments

@L1nBra
Copy link

L1nBra commented May 23, 2025 •
edited
Loading

Description
Visually present text for the element which is the name of it, has to be announced for the user, using assistive technology. In case the name is very long or would be better to have it announced with more descriptive text, then at least the start of the visible name should be announced the same for the user.

Preconditions
Observability -> Synthetics -> Settings page.
Alerting tab is activated.
Use Screen Reader (NVDA).

Steps to reproduce

1.Navigate to Default connectors.
2.Observe page and screen reader.

UI elements + NVDA Speech Viewer
Image

Actual Result

  • Visual name (Default connectors) of field is different from announced one (Tags).

Expected Result

  • Visual name of field and announced one are the same: "Default connectors combo box..."

Meta Issue

Version: 9.0.1

OS: Windows 11 Pro

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

Screen reader: NVDA

WCAG or Vendor Guidance (optional)

Related to: https://github.com/elastic/kibana-team/issues/1655
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot added the needs-team Issues missing a team label label May 23, 2025
@L1nBra L1nBra added WCAG A impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. defect-level-2 Serious UX disruption with workaround obs-accessibilty A11Y issues in the Obs. solution. labels May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
defect-level-2 Serious UX disruption with workaround impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. needs-team Issues missing a team label obs-accessibilty A11Y issues in the Obs. solution. Project:Accessibility WCAG A
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elasticmachine @L1nBra