Skip to content

fix(ui5-view-settings-dialog): ensure proper focus management in filter view#13092

Open
hinzzx wants to merge 1 commit intomainfrom
vsd-fi-focus-fix
Open

fix(ui5-view-settings-dialog): ensure proper focus management in filter view#13092
hinzzx wants to merge 1 commit intomainfrom
vsd-fi-focus-fix

Conversation

@hinzzx
Copy link
Contributor

@hinzzx hinzzx commented Feb 16, 2026

Overview

Two issues were identified in the ViewSettingsDialog component when testing our ACC Samples in the Accessibility Hub:

  1. Focus is lost when entering the filter options view - When clicking on a filter item to see its options (second-level navigation), focus was not properly managed, leaving users of assistive technologies without a clear focus point.

  2. Tab order goes to Cancel first in some situations - After entering filter options, pressing Tab would sometimes move focus to the Cancel button before the OK button, which is inconsistent with expected dialog behavior.

What We Did

  • Added @query decorators to reference the filter list
  • after rendering completes, focus is set on the first selected item (if any) or the first item in the filter options list
  • when navigating back to the filter list, focus is set on the first item

What This Fixes

  • Focus management — Focus is now properly set when entering filter options (second-level view)
  • Tab order — Tab correctly moves from filter options to the OK button (Emphasized) first, then to Cancel
  • Keyboard navigation — Users can navigate the filter workflow entirely with keyboard
  • Screen reader experience — Assistive technology users receive proper focus context when navigating between filter views

Before

2026-02-16_14-25-22 (1)

After

2026-02-16_13-51-28 (1)

@ui5-webcomponents-bot
Copy link
Collaborator

@ui5-webcomponents-bot ui5-webcomponents-bot temporarily deployed to preview February 16, 2026 12:15 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants