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

[Search:AppSearch:Engines:SearchUI:Search Experience page]For Search field announcement of results found and not found #202651

Open
L1nBra opened this issue Dec 3, 2024 · 1 comment
Labels
defect-level-3 Moderate UX disruption or potentially confusing deprecated-in-9.0 Feature marked as deprecated in v9.0. This label is used within the a11y project Project:Accessibility Team:Search WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Dec 3, 2024

Description
User should hear correct one announcement. Either the results were found or results were not found. Not both at once.

Preconditions
Stateful App Search -> Engines -> Search UI -> Search Experience page is opened.
Engine is added.
Use Screen Reader (NVDA).

Steps to reproduce

1.Using only keyboard navigate to Search field by pressing Tab key.
2.Enter text which would provide results (f.e.: test).
3.Observe screen reader

UI elements + NVDA Speech Viewer
Image

Actual Result

  • When user finishes entering word test, screen reader announces "No results are available 10 results are available...".

Expected Result

  • Announcement is made about results found "10 results are available...".

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 130.0.6723.70 (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 Dec 3, 2024
@L1nBra L1nBra added WCAG A Team:Search defect-level-3 Moderate UX disruption or potentially confusing labels Dec 3, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 3, 2024
@alexwizp alexwizp added the deprecated-in-9.0 Feature marked as deprecated in v9.0. This label is used within the a11y project label Dec 5, 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 deprecated-in-9.0 Feature marked as deprecated in v9.0. This label is used within the a11y project Project:Accessibility Team:Search WCAG A
Projects
None yet
Development

No branches or pull requests

3 participants