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

Accessibility: Screen Reader for "Destination Folder" is read in incorrect order #7926

Open
andyleejordan opened this issue Dec 15, 2023 · 3 comments
Labels
accessibility up for grabs No one volunteered to fix the issue. If you are interested, comment with "I want to fix this issue"

Comments

@andyleejordan
Copy link

WiX Version

Unsure

.NET or MSBuild or Visual Studio Version

N/A

HeatWave Version

N/A

Windows Version

Win11

Repro Repo

No response

Repro Steps

  1. Launch installer built with WiX (such as PowerShell's, where this accessibility bug was originally reported)
  2. Tab on installer's "Next" button
  3. Run NVDA version 2021.3
  4. Press enter on the next button in welcome screen and check if the screen reader is announcing the info present in the Destination Folder in correct order.

Actual Result

When pressing enter on the next button in welcome screen, screen reader is announcing the information in incorrect order as "PowerShell 7-x86 Setup, Click Next to install to the default folder or click Change to choose another. Destination Folder, Install PowerShell 7-x86 to: Next button Alt+n"

Similar issue is also observed in JAWS version 2021.2103.174 ILM
Similar issue is also observed in following screens
OptionalActions
MicrosoftUpdate
Completion

Expected Result

When pressing enter on the next button in welcome screen, screen reader should the information in incorrect order as "PowerShell 7-x86 Setup, Destination Folder, Click Next to install to the default folder or click Change to choose another. Install PowerShell 7-x86 to: followed by the data in the edit field and lastly Next button Alt+n"

@msftedad
Copy link

could you please provide the tentative ETA for fixing this issue?

@barnson barnson added accessibility up for grabs No one volunteered to fix the issue. If you are interested, comment with "I want to fix this issue" and removed triage labels Jan 2, 2024
@msftedad
Copy link

msftedad commented Feb 8, 2024

Hi @barnson , Is there any update on this issue?

@wmanning
Copy link

wmanning commented Feb 8, 2024

@msftedad Again no one assigned and tagged as "up for grabs" meaning not being worked on and won't be worked on until someone volunteers to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility up for grabs No one volunteered to fix the issue. If you are interested, comment with "I want to fix this issue"
Projects
None yet
Development

No branches or pull requests

4 participants