Description
For user using assistive technology it's better to hear the element name and placeholder text which would be either an example what to enter or explaining more about the search field. And when Search fields has instructions (text below it) - it should be announced for the user.
Preconditions
Stateful Search Applications page is opened.
Search application is added.
Use Screen Reader (NVDA).
Steps to reproduce
1.Using only keyboard Navigate to Search Applications field by pressing Tab key.
2.Observe screen reader.
UI element + NVDA Speech Viewer
Actual Result
Field is announced as "Search Applications edit Search Applications blank" - text is duplicated due to the name of the field an Placeholder text being identical. No announcement about additional text below the field.
Expected Result
Field is announced together with additional text: "Search Applications edit Locate a search application via name blank".
Meta Issue
Kibana Version: 8.17.0-SNAPSHOT
OS: Windows 11 Pro
Browser: Chrome Version 130.0.6723.70 (Official Build) (64-bit)
Description For user using assistive technology it's better to hear the element name and placeholder text which would be either an example what to enter or explaining more about the search field. And when Search fields has instructions (text below it) - it should be announced for the user.
Preconditions Stateful Search Applications page is opened. Search application is added. Use Screen Reader (NVDA).
Steps to reproduce
1.Using only keyboard Navigate to Search Applications field by pressing Tab key. 2.Observe screen reader.
UI element + NVDA Speech Viewer
Actual Result
Expected Result
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