[PWA Builder]: Keyboard Focus Not Visible on Action Items Expandable Button.

[Anshi0420]

What happened?

When navigating using the keyboard, the focus indicator is not visible on the Action items expandable button.

How do we reproduce the behavior?

Repro Steps:

1. Open the above URL.
2. Navigate to the Action Items expandible button with keyboard.
3. Observe the keyboard focus.

What do you expect to happen?

The Action items expandable button should clearly indicate keyboard focus when navigated to using the keyboard, following accessibility standards.

What environment were you using?

Test Environment:
OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.461)
Edge Browser: Version 123.0.2400.1 (Official build) dev (64-bit)
URL: https://www.pwabuilder.com/reportcard?site=https://webboard.app

Additional context

Note:

1. Keyboard focus is not visible on the View details button present on this page.
2. Keyboard focus is not visible on the close button inside the Share dialog.

User Impact:
Users who rely on keyboard navigation, such as those with motor disabilities or who prefer not to use a mouse, may find it difficult to determine which element is currently focused on the screen.

WCAG Reference:
https://www.w3.org/WAI/WCAG22/Understanding/focus-visible

Attachments:

MAS2.4.7_Keyboard.Focus.Not.Visible.on.Action.Items.Expandable.Button.mp4

NOTE1_KB.not.visible.on.view.details.button.mp4

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .