microsoft / microsoft/AdaptiveCards
[Adaptive Cards- Blog] : Keyboard focus is landing separately on image Link and announcing the WinUI 3 rendering link. Also, on activating it using enter key same blog page is getting opened.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Target Platforms
Other
SDK Version
1.6
Application Name
Adaptive Cards
Problem Description
Test Environment:
URL: https://adaptivecards.io/
OS Version: Dev (OS Build 27695.1000)
Browser Version: Version 130.0.2849.1 (Official build) dev (64-bit)
Pre-Requisite:
Navigate through keyboard only.
Repro steps:
- Open the above URL in the edge dev browser.
- Navigate to the 'Blog' option and press enter key to activate it.
- Press tab key and navigate to the blog.
- Press tab key and navigate the screen and observe the issue.
Actual Result:
Keyboard focus is landing separately on image Link and announcing the WinUI 3 rendering link. Also, on activating it using enter key same blog page is getting opened.
Expected Result:
Keyboard focus should not land separately on the links. When the focus is on the entire blog then on pressing tab key again entire keyboard focus should land on the Image and WinUI 3 link.
Note:
Same issue is repro while navigating on the J.P Roka link.
User Impact:
It will impact the keyboard user as they will get confuse if the focus lands on the links separately as on activating both link same page is getting open due to this extra time and effort will be taken for them.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/focus-order
Have feedback to share on Bugs ? please tag bug as “A11yRCA” and add your feedback in the comment section
Screenshots
https://github.com/user-attachments/assets/af14f59c-2cec-435f-b4e6-0417bb03657f
Card JSON
NA
Sample Code Language
No response
Sample Code
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at https://adaptivecards.io/ and reproduce the Blog keyboard-navigation flow in Edge Dev using only the keyboard. Inspect the Blog entries, including the WinUI 3 rendering and J.P. Roka links, and trace how focus and activation behave. Done means each blog item has the intended focus order without duplicate link activation or reopening the same page.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100