microsoft / microsoft/AdaptiveCards

[Rendering][Authoring][Designer] aria-label attribute is not available for elements; it is necessary for screen reader support

Open
#8,394 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Schema Bug
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

Target Application

Widgets Board

Application Operating System

Windows

Schema Version

Latest

Problem Description

When designing any UI that isn't a straightforward document - you need different affordances for using the UI for users who can see and for users who can't. When you can see the UI layout, hover over elements and see tooltips - you can infer much more than if you use it with a screen reader. Aria-label is the web version of the most basic screen reader affordance and it is missing in all or most cases from adaptive cards at least based on what I can infer from the designer. The aria-label may be the narrated description of an icon seen on a button that makes sense to hear. You can provide a tooltip for some elements like buttons, but a tooltip should provide more information than what the button itself already provides and should not repeat what's already seen when looking at a button, while an aria-label might serve that purpose. Also, it may be useful for more than just a button. Labels (TextBlock), Input.Text, Input.Number, etc and any other elements should support both tooltips and aria-label.

Expected Outcome

Aria-label or AutomationProperties.Name-like label for screen readers available on any element.

Actual Outcome

missing

Card JSON
-
Repro Steps

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

No source file, test, or renderer entry point is named. Start by clarifying which Adaptive Cards elements and platforms must expose the label, then trace the designer and rendering paths; done means a defined set of elements consistently provides an aria-label or AutomationProperties.Name equivalent for screen readers.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
accessibility, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.