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.

Sign up for GitHub

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

Jump to bottom

Expanders are presented as "group collapsed" in Narrator instead of presenting Name/HelpText #12317

Closed
carlos-zamora opened this issue Feb 1, 2022 · 4 comments
Closed

Expanders are presented as "group collapsed" in Narrator instead of presenting Name/HelpText #12317

carlos-zamora opened this issue Feb 1, 2022 · 4 comments
Labels
Area-Accessibility Issues related to accessibility Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Tracking-External This bug isn't resolved, but it's following an external workitem.

Comments

@carlos-zamora
Copy link
Member

Windows Terminal version

1.13.10321.0

Windows build number

22548.1002

Other Software

None

Steps to reproduce

  1. Open Narrator or Accessibility Insights
  2. Navigate to an Expander in the Settings UI (i.e. "Startup" > "When Terminal starts")

Expected Behavior

The setting name/description should be exposed as the AutoProp.Name/HelpText respectively.

Actual Behavior

Name/HelpText are undefined.
@carlos-zamora carlos-zamora added Issue-Bug It either shouldn't be doing this or needs an investigation. Area-Accessibility Issues related to accessibility Product-Terminal The new Windows Terminal. labels Feb 1, 2022
@ghost ghost added the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Feb 1, 2022
@carlos-zamora
Copy link
Member Author

This will be fixed after updating to MUX 2.8 because it was fixed in microsoft/microsoft-ui-xaml#6032.

@carlos-zamora carlos-zamora added the Tracking-External This bug isn't resolved, but it's following an external workitem. label Feb 1, 2022
@carlos-zamora carlos-zamora added this to the Terminal v1.14 milestone Feb 1, 2022
@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Feb 1, 2022
@zadjii-msft
Copy link
Member

Got a build with 2.8. This wasn't fixed.

@zadjii-msft zadjii-msft added the zInbox-Bug Ignore me! label Mar 10, 2022
@zadjii-msft zadjii-msft removed the zInbox-Bug Ignore me! label Mar 24, 2022
@zadjii-msft zadjii-msft modified the milestones: Terminal v1.14, 22H1 Apr 28, 2022
@zadjii-msft zadjii-msft mentioned this issue May 2, 2022
Closed
@zadjii-msft
Copy link
Member

Duping this up to #13019, since that's the a11y tracking thread.

/dup #13019

@ghost
Copy link

ghost commented May 2, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed May 2, 2022
@ghost ghost added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label May 2, 2022
@zadjii-msft zadjii-msft removed this from the 22H1 milestone May 2, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Accessibility Issues related to accessibility Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Tracking-External This bug isn't resolved, but it's following an external workitem.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DHowett @carlos-zamora @zadjii-msft