Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Designer] Bug 33488858: [Adaptive Cards - ExpenseReport.Json]: The name property of focusable element must not be NULL. #7628

Closed
aaagrawal opened this issue Jul 4, 2022 · 3 comments
Labels
A11ySev3 Accessibility issue with severity 3 A11yTTValidated A11yWCAG Accessibility issue that affects compliance AdaptiveCards_Universal a11y tag Area-Accessibility Bugs around feature accessibility Area-Designer Bug HCL-AdaptiveCards-Universal a11y tag HCL-AdaptiveCards-WPF Used by accessibility team for scorecard categorization HCL-E+D Product-AC

Comments

@aaagrawal
Copy link

Problem Description

Bug 33488858: [Adaptive Cards - ExpenseReport.Json]: The name property of focusable element must not be NULL.

Test Environment:

Application: Adaptive Cards
OS version: Dev (OS Build 21387.1)

Application Version: 2.7.2105.11001

Tool Used: Accessibility Insights

Repro steps:

  1. Launch the Adaptive Card application.

  2. Adaptive Card UWP Visualizer screen starts appearing.

  3. Navigate to ExpenseReport.Json button by using Tab key and activate it.

  4. Expense approval adaptive card will be appeared on right sight of the pane.

  5. Navigate to Expense approval card by using Tab key.

  6. Navigate to 'Show History' button with Tab key.

  7. Run K4D on Show History button and verify the issue.

Actual Result:
Name property is defined NULL of 'Show History' button.

Expected Result:
Name property must be defined for the 'Show History' button.

User Experience:
It will not impact the screen reader users if Name property of any control will be defined NULL.

Card JSON

Designer Bug. Repro on UWP Adaptive Card visualizer

Screenshot

No response

@palitsourish palitsourish added Area-Accessibility Bugs around feature accessibility A11ySev3 Accessibility issue with severity 3 HCL-E+D Product-AC HCL-AdaptiveCards-WPF Used by accessibility team for scorecard categorization labels Jul 8, 2022
@Apoorva076 Apoorva076 added the A11yWCAG Accessibility issue that affects compliance label Jul 27, 2022
@vagpt
Copy link
Collaborator

vagpt commented Jan 9, 2024

Hi @anna-dingler

This issue is still repro at our end so is there any plan whether Dev will work on it or not?

image

@anna-dingler
Copy link
Contributor

Hi @vagpt,

I will speak with my team about budgeting for this bug.

Thanks,
Anna

@vagpt
Copy link
Collaborator

vagpt commented Dec 23, 2024

This issue is now tracking with #9076 hence closing this issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A11ySev3 Accessibility issue with severity 3 A11yTTValidated A11yWCAG Accessibility issue that affects compliance AdaptiveCards_Universal a11y tag Area-Accessibility Bugs around feature accessibility Area-Designer Bug HCL-AdaptiveCards-Universal a11y tag HCL-AdaptiveCards-WPF Used by accessibility team for scorecard categorization HCL-E+D Product-AC
Projects
None yet
Development

No branches or pull requests

6 participants