[accessibility-1217621]: Keyboard focus gets lost on the page which opens after activating "Data Explorer" menu item present under 'Overview' page.

[satya07sb]

This PR addresses an issue where keyboard focus is lost when navigating to the Data Explorer page from the Overview page in Azure Cosmos DB. The problem was that after activating the "Data Explorer" menu item, the page did not correctly set focus on the expected element, impairing keyboard navigation.

Preview this branch

621.mp4

[sevoku]

Is there a specific reason we want to focus the refresh button initially? The first focusable element would rather be the first button in the toolbar. However from usability perspective it'd make more sense to focus the big "New Container" button, users who don't have created any container yet, can just proceed from there and others need only to hit Tab once to reach their data. Thoughts?

[satya07sb]

Is there a specific reason we want to focus the refresh button initially? The first focusable element would rather be the first button in the toolbar. However from usability perspective it'd make more sense to focus the big "New Container" button, users who don't have created any container yet, can just proceed from there and others need only to hit Tab once to reach their data. Thoughts?

As per your suggestion it will make more sense; However, the ticket specifies that the focus should be on the refresh button when opening the Data Explorer.
Ticket: accessibility-1217621

[jawelton74]

Is there a specific reason we want to focus the refresh button initially? The first focusable element would rather be the first button in the toolbar. However from usability perspective it'd make more sense to focus the big "New Container" button, users who don't have created any container yet, can just proceed from there and others need only to hit Tab once to reach their data. Thoughts?

As per your suggestion it will make more sense; However, the ticket specifies that the focus should be on the refresh button when opening the Data Explorer. Ticket: accessibility-1217621

I agree with Sevo. Let's seek clarification from the accessibility team.