Description
It is enough for user to hear the same information once upon reaching element. In this case paging, pages for search results.
Especially for the users using assistive technology.
Preconditions
Stateful App Search -> Engines -> Documents page is opened.
Engine is added.
Use Screen Reader (NVDA).
Steps to reproduce
1.Navigate to page 2 button while pressing tab key.
2.Observe screen reader.
3.Navigate to any other page (f.e. button 3) and press Enter.
4.Observe screen reader.
5.Navigate to Number of results combo box.
6.Press Enter.
7.Select any option (f.e.: 40).
8.Observe screen reader.
UI elements + NVDA Speech Viewer
[step 2]
[step 4]
[step 8]
Actual Result
For all cases announcement is duplicated.
"Search results paging at top of results navigation landmark Search results paging at top of results list..."; "page 3 of 58 page 3 of 58".
Expected Result
Announcement for paging, pages should be made only one time.
Meta Issue
Kibana Version: 8.17.0-SNAPSHOT
Screen reader: NVDA
OS: Windows 11 Pro
Browser: Chrome Version 130.0.6723.70 (Official Build) (64-bit)
Description It is enough for user to hear the same information once upon reaching element. In this case paging, pages for search results. Especially for the users using assistive technology.
Preconditions Stateful App Search -> Engines -> Documents page is opened. Engine is added. Use Screen Reader (NVDA).
Steps to reproduce
1.Navigate to page 2 button while pressing tab key. 2.Observe screen reader. 3.Navigate to any other page (f.e. button 3) and press Enter. 4.Observe screen reader. 5.Navigate to Number of results combo box. 6.Press Enter. 7.Select any option (f.e.: 40). 8.Observe screen reader.
UI elements + NVDA Speech Viewer
[step 2]
[step 4]
[step 8]
Actual Result
Expected Result
Meta Issue
Kibana Version: 8.17.0-SNAPSHOT
Screen reader: NVDA
OS: Windows 11 Pro
Browser: Chrome Version 130.0.6723.70 (Official Build) (64-bit)
WCAG or Vendor Guidance (optional)
Related to: https://github.com/elastic/search-team/issues/8256