microsoft / microsoft/AdaptiveCards
[Adaptive Cards - Elements Properties] - Heading is not defined for the 'Text Block, Layout and Styles' under elements properties pane.
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)
Screen Reader: Narrator
Repro Steps:
- Open the above URL on the Edge Dev browser.
- Press tab key and navigate to the Designer tab item and press enter key to select it.
- Press tab key navigate to the editor section and select any field.
- Press tab key and navigate to the 'Element Property' button and press enter key to activate it.
- Navigate the pane using 'H' key and observe the issue.
Actual Result:
Under the 'Elements Properties' pane, no heading is defined for the 'Text Block, Layout and styles'. If a screen reader user navigates using h key in heading mode. then it is not announcing the any information about the heading.
Expected Result:
'Text Block, Layout and styles' should be defined as heading so that when the screen reader user navigate using h key then it should navigate on each label and announced the heading information.
Note:
While in developer mode, Publish Adaptive Card Schema is also not defined as heading.
User Experience:
Screen reader users often rely on heading shortcuts to efficiently navigate a page. Without proper headings, they may struggle to quickly locate and access specific sections of content, making their experience less efficient.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships
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/b2a14cfd-f345-4aa8-b957-919cf2ca0ba2
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
Open https://adaptivecards.io/ in Edge Dev and reproduce the issue in the Designer with Narrator. Inspect the Elements Properties pane and the developer-mode Publish Adaptive Card Schema section. Done means heading navigation announces Text Block, Layout and Styles and the noted publish section as headings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100