microsoft / microsoft/AdaptiveCards

[Adaptive Cards> FlightUpdate.json]: Focus order is not appearing in logical sequence on passengers and seats name.

Open
#8,978 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11yCT A11yMissing_HCLReviewed A11ySev3 A11yWCAG AdaptiveCards_Web Area-Accessibility Area-Renderers Bug HCL-AdaptiveCards-Web HCL-E+D MissingReviewedDeprecated Product-AC
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

Target Platforms

UWP

SDK Version

1.0.1.0

Application Name

Adaptive Cards

Problem Description

Test Environment:
Application: Adaptive Cards Universal
OS Build: 24H2 (OS Build 26252.5000)
App Version: 1.0.1.0
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 'FlightUpdate.json' through tab key and activate it.
  4. Now, navigate to 'Passengers' name through up/down arrow key.
  5. Observe the issue.

Actual Result:
Focus order is not appearing in logical sequence on passengers and seats name text when user navigates in the scan mode of narrator through up/down arrow key.

Expected Result:
Focus order is not appearing in logical sequence on passengers and seats name text when user navigates in the scan mode of narrator through up/down arrow key.

It should be something like Sarah Hum > 14A > Jeremy GoldBerg > 14B > EVAN > 14 C

User Impact:
Screen reader user will get impacted as user will have difficulty in navigating or in making proper track of the content.

WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence

Have feedback to share on Bugs ? please tag bug as “A11yRCA” and add your feedback in the comment section.

Screenshots
In scan mode, focus order is not in logical order

https://github.com/user-attachments/assets/85fe4d43-3e21-4636-a27e-2a245830a647

Card JSON
NA
Sample Code Language

No response

Sample Code

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by opening the FlightUpdate.json card in the Adaptive Card Visualizer on UWP and reproduce the sequence with Narrator scan mode. Compare the order of passenger and seat names with the expected Sarah Hum > 14A > Jeremy GoldBerg > 14B > EVAN > 14 C sequence. Done means the focus order is logical and screen-reader navigation matches that sequence.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.