[A11y - Adaptive Card] Keyboard focus partially visible on close button and less tooltip of this button in action response message

[sherryzhao11]

Steps to reproduce

adaptive card Json
{ "type": "AdaptiveCard", "$schema": "https://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "TextBlock", "weight": "Lighter", "text": "Aug 15, 2024", "wrap": true, "style": "heading", "size": "Medium" } ], "actions": [ { "type": "Action.Submit", "title": "Approve", "id": "approveAction", "associatedInputs": "auto", "data": { "path": "biteLayer/requestAction" } } ] }

Expected behavior

1. The keyboard focus outline should be visible on all four sides of the close button when it receives keyboard focus, ensuring compliance with accessibility standards
2. issue should be fixed in both default and high-contrast theme
3. The close button should have a meaningful tooltip
4. After announcing the success message, the screen reader should announce the close button and avoid reading unrelated card details

Actual behavior

1. After send Action.Submit, the Teams application displays a response

message with a close button. While navigating using the keyboard, the focus outline on the close button is not fully visible. It is only visible on two sides of the close icon, while the other two sides remain obscured. This issue persists in both the application's default and high-contrast theme of the application. 2. the close button does not have a tooltip when hovered over with a mouse, which impacts accessibility for users relying on assistive technologies. 4. When using a screen reader, after the success message is announced, the screen reader does not directly announce the close button.

Error details

No response

[microsoft-github-policy-service]

Hi sherryzhao11! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

[sayali-MSFT]

@sherryzhao11, Thank you for your inquiry about your Teams app development issue!

We were able to reproduce the issue in the Desktop Microsoft Teams version 25007.2000.3341.2815. We have reported this as a bug for further investigation.

We will keep you updated as soon as we receive further information. Thank you for bringing this to our attention!