{Freeway-Bug} [Adaptive Cards> FlightItinerary.json]: Focus order is not in sequential way in FlightItinerary.json card

[vaishali1397]

Target Platforms

UWP

SDK Version

3.0.2206.2001

Application Name

Adaptive Cards

Problem Description

Test Environment:
OS version: 22H2 (Build 25182.1010)
Browser: Edge Dev (106.0.1356.0)
Application: AdaptiveCardVisualizer
Application Version: 3.0.2206.2001
Screen Reader: Narrator

Repro Steps:

1. Open the Adaptive Card Visualizer application.
2. Turn on the Narrator through Ctrl+ windows+ enter key and press caps lock + space bar key to turn on the scan mode.
3. Navigate to the 'FlightItinerary.json' through tab key and activate it.
4. Now, navigate to 'San Francisco' and 'Amsterdam through up/down arrow key.
5. Observe the issue.

Actual Result:
On FlightItinerary.json card, focus order is not in sequential manner. Focus order is of San Francisco> Amsterdam> SFO> Image to> AMS.

Expected Result:
On FlightItinerary.json card, focus order should be in sequential manner**. Focus order should be in a way San Francisco> SFO>Image to> Amsterdam> AMS**

User Impact:
People with cognitive disability will get impacted if focus order is not in sequential way due to which user will have difficulty in making track of the content properly..

MAS Reference link:
https://liquid.microsoft.com/Web/Object/Read/MS.Accessibility/Requirements/01.03.02

“Have feedback to share on Bugs? Please help fill Trusted Tester Bug Feedback (office.com) “

Screenshots

MAS1.3.2.Focus.order.is.not.in.sequential.way.mp4

Card JSON

NA

Sample Code Language

No response

Sample Code

No response

[PERUAMLLABALAKRISHNA]

Focus order issue is observed after acting the set due date control.

Focus.order.is.not.correct.after.activating.the.set.due.date.mp4

[vaishali1397]

Issue is repro'ing in below test environment, hence reactivating the bug.
Test Environment:
OS version: 22H2(Build 25272.1000)
Application: Adaptive Cards Visualizer (3.0.2210.26001 (latest) build.)

[JeanRoca]

This issue has been fixed and will be included in our next release. I am closing this issue for now. Once new version is available, if the issue persists please open a new issue to track.

[vaishali1397]

Issue has been fixed in below test Environment, hence Adding A11yTTValidated tag.
Test Environment:
OS Version: 22H2 (Build 25314. 1010)
Application: Adaptive Card Visualizer (Version 3.2.2303.22003)

PFA for Reference: Adaptive cards UWP~ Fixed issue.mp4

Adaptive.cards.UWP.Fixed.issue.mp4