microsoft / microsoft/AdaptiveCards
[Rendering][Authoring][Designer] aria-live attribute is not available for elements; it is necessary for screen reader support
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
Latest
Application Name
Windows widgets board
Problem Description
Widget adaptive cards don't seem to support aria-live attribute, which is necessary to narrate state changes and events that aren't directly represented in visual UI. Especially for a small UI like a widget - some state may be clearly visible to non-disabled usersm but requires more descriptive narration when used with a screen reader like Narrator or JAWS. Aria-live seems to be the solution for doing that in HTML.
Example of how a similar functionality works in a XAML app:
// Narrator confirmation of action
AutomationPeer^ peer = FrameworkElementAutomationPeer::FromElement(annotateCanvas);
if (peer != nullptr)
{
peer->RaiseNotificationEvent(
AutomationNotificationKind::ActionCompleted,
AutomationNotificationProcessing::MostRecent,
GetLocalizedString(L"UndoButton/AutomationProperties/Name"),
L"UndoRedo");
}
Screenshots
No response
Card JSON
...
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
No file, test, entry point, or concrete implementation scope is named. Start by reviewing how Adaptive Cards render accessibility properties on the Windows widgets board and compare the requested aria-live behavior with the linked HTML and XAML notification examples; done should define and implement a supported way to announce relevant state changes to screen readers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100