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

{Freeway-Bug} [Adaptive Cards> InputsWithValidation.json> Input.Toggle]: Voice access user is not able to access 'Start time' edit field through 'Move to Start time' command. #7521

Closed
vaishali1397 opened this issue Jun 13, 2022 · 3 comments · Fixed by #8032
Assignees
Labels
A11ySev2 Accessibility issue with severity 2. This may impact the accessibility score A11yTTValidated A11yWCAG Accessibility issue that affects compliance Area-Accessibility Bugs around feature accessibility Area-Renderers Bug HCL-AdaptiveCards-Universal a11y tag HCL-AdaptiveCards-WPF Used by accessibility team for scorecard categorization HCL-E+D Platform-XAML Bugs or features related to Xaml Renderer Product-AC
Projects

Comments

@vaishali1397
Copy link
Collaborator

Target Platforms

UWP

SDK Version

3.0.2206.2001

Application Name

Adaptive Cards

Problem Description

Problem Description
Test Environment:
OS Version: 22H2 (Build 25126.1000)
Application: Adaptive Cards UWP
Application Version: 3.0.2206.2001
Tool: Voice access

Repro Steps:

  1. Turn on voice access.
  2. Open Adaptive Cards UWP application.
  3. Command: Voice access wake up'
  4. Command: Show Numbers
  5. Select particular number for 'InputsWithValidation.json'
  6. Command: Move to Start time
  7. Observe the issue.

Actual Result:
Voice access user is not able to access 'Start time' edit field through 'Move to Start time' command instead it is accessible through 'Move to 16' command.

Expected Result:
Voice access user should be able to access 'Start time' edit field through 'Move to Start time' command.

User Impact:
People with limited mobility (cerebral palsy, quadriplegia) who use Voice Access will get impacted as user will not be able to interact with the Start time edit field due to which they will not be able to make proper track of the controls.

MAS reference link:
[No Disruption of Accessibility Features - Liquid (microsoft.com)]

Have feedback to share on Bugs? Please help fill Trusted Tester Bug Feedback (office.com)"

Screenshots

MAS4.3.1.Move.to.Start.time.command.is.not.getting.performed.mp4

MAS4 3 1 Voice access user is not able to access Start time comboedit field

Card JSON

NA

Sample Code Language

No response

Sample Code

No response

@ghost ghost added this to Not Triaged in Triage Jun 13, 2022
@paulcam206 paulcam206 added Platform-XAML Bugs or features related to Xaml Renderer Area-Accessibility Bugs around feature accessibility A11ySev2 Accessibility issue with severity 2. This may impact the accessibility score labels Jun 13, 2022
@paulcam206 paulcam206 moved this from Not Triaged to P2 in Triage Jun 13, 2022
@palitsourish palitsourish added HCL-E+D Product-AC HCL-AdaptiveCards-WPF Used by accessibility team for scorecard categorization labels Jun 14, 2022
@vaishali1397 vaishali1397 self-assigned this Sep 13, 2022
@vaishali1397 vaishali1397 added the A11yWCAG Accessibility issue that affects compliance label Sep 13, 2022
Triage automation moved this from P2 to Closed Nov 9, 2022
@vaishali1397 vaishali1397 changed the title [Adaptive Cards> InputsWithValidation.json> Input.Toggle]: Voice access user is not able to access 'Start time' edit field through 'Move to Start time' command. {Freeway-Bug} [Adaptive Cards> InputsWithValidation.json> Input.Toggle]: Voice access user is not able to access 'Start time' edit field through 'Move to Start time' command. Jan 13, 2023
@vaishali1397
Copy link
Collaborator Author

Issue is repro'ing in below test environment, hence reactivating the bug.
Test Environment:
OS version: 22H2(Build 25272.1000)
Application: Adaptive Cards Visualizer (3.0.2210.26001 (latest) build.)

@vaishali1397 vaishali1397 reopened this Jan 13, 2023
Triage automation moved this from Closed to Not Triaged Jan 13, 2023
@JeanRoca
Copy link
Contributor

This issue has been fixed and will be included in our next release. I am closing this issue for now. Once new version is available, if the issue persists please open a new issue to track.

Triage automation moved this from Not Triaged to Closed Jan 19, 2023
@vaishali1397
Copy link
Collaborator Author

Issue has been fixed in below test Environment, hence Adding A11yTTValidated tag.
Test Environment:
OS Version: 22H2 (Build 25314. 1010)
Application: Adaptive Card Visualizer (Version 3.2.2303.22003)
PFA for Reference:
https://user-images.githubusercontent.com/104483005/228221572-b7057514-d403-41c4-978d-24e6900ccc1e.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A11ySev2 Accessibility issue with severity 2. This may impact the accessibility score A11yTTValidated A11yWCAG Accessibility issue that affects compliance Area-Accessibility Bugs around feature accessibility Area-Renderers Bug HCL-AdaptiveCards-Universal a11y tag HCL-AdaptiveCards-WPF Used by accessibility team for scorecard categorization HCL-E+D Platform-XAML Bugs or features related to Xaml Renderer Product-AC
Projects
Triage
Closed
Development

Successfully merging a pull request may close this issue.

6 participants