microsoft / microsoft/microsoft-ui-xaml
ContentDialog's Title does not have HeadingLevel automation property set
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
### Describe the bug
The title for a content dialog should have the [AutomationProperties.HeadingLevel](https://learn.microsoft.com/en-us/uwp/api/windows.ui.xaml.automation.automationproperties.headinglevel?view=winrt-26100) set to something (probably Level1 for simplicity).
### Why is this important?
Users who rely on screen reader will feel difficulty in analyzing the structure of the page, if visually appearing heading is not defined as heading programmatically.
WCAG Reference link:
[1.3.1 Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships)
### Steps to reproduce the bug
1. Open WinUI 2 Gallery > Dialogs and Flyouts > [ContentDialog](winui2gallery://item/ContentDialog)
2. Click "Show dialog"
3. Use accessibility insights to check the heading level of the title of the ContentDialog
### Actual behavior
no heading level set
### Expected behavior
heading level should be set
### Screenshots
### NuGet package version
None
### Windows version
_No response_
### Additional context
Originally filed on Windows Terminal: https://github.com/microsoft/terminal/issues/19686
Contributor guide
Research direction
Start with the ContentDialog entry in WinUI 2 Gallery under Dialogs and Flyouts, then trace how the dialog title is defined and exposed to Accessibility Insights. Done means the title reports an appropriate AutomationProperties.HeadingLevel, with the existing ContentDialog behavior otherwise unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- accessibility, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100