[Power toys-Image resizer]: Edit Buttons in Image Resizer Not Associated with Their Names and Dimensions.

[Anshi0420]

Microsoft PowerToys version

0.86.0

Installation method

PowerToys auto-update

Running as admin

None

Area(s) with issue?

Image Resizer

Steps to reproduce

Test environment:
OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.1340)
Power toys version: v0.86.0
Screen Reader: Narrator

Repro Steps:

1. Open the Power Toys app in the desktop.
2. Select the Image Resizer option from left navigation pane.
3. Turn on narrator using Ctrl + Win + Enter.
4. Now navigate to the Edit buttons present below the Add new buttons.
5. Observe the issue.

User Experience:
Screen reader users will be unable to understand which button controls which dimension, making it difficult or impossible to resize images effectively.

Note:
Same issue is also repro for delete button.

Attachments:

319933907-3c3a08d0-692b-4158-8c1e-576a4ca05d1d.mp4

Guideline reference:
https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships

✔️ Expected Behavior

Each edit button in the image resizer should have a descriptive label, either visually or programmatically, that clearly identifies its function and the dimensions it controls (e.g., "Set Width to 500px", "Set Height to 300px").

❌ Actual Behavior

The edit buttons in the image resizer tool are not properly labeled or associated with the corresponding image dimensions (e.g., width, height).

Other Software

No response

[similar-issues-ai]

We've found some similar issues:

• [Power Toys-Image resizer]: The edit and delete buttons present in the image sizes section are not descriptive in nature. #32255 , similarity score: 86%
• [Power Toys-Fancy zones>Image resizer]: Add new size button is not associated with its label. #32256 , similarity score: 83%
• [Power Toys-File Explorer>Image resizer]: No name is defined for the check boxes which is present on the image resizer dialogue. #32258 , similarity score: 82%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[htcfreek]

@daverayment
Your contribution is welcome and thank you for your work on this. Feel free to open a PR. If you have any further questions don't worry to ask them.

[drawbyperpetual]

@daverayment @htcfreek - Apologies for not noticing this earlier - I've worked on this and will raise a PR shortly. I hope there hasn't been any duplicated effort!

[daverayment]

@drawbyperpetual I've just finished this myself, along with several other fixes, and was about to submit my own PR 😬

I'm not sure what's best here. My PR differs in a number of ways from yours, and covers several more issues I found, including problems with the ViewModel, ImageSize class etc.

I also used both AutomationProperties.Name and AutomationProperties.FullDescription for the accessibility text, rather than HelpText.

I will submit the PR then we can compare and contrast, maybe?

[daverayment]

@drawbyperpetual @htcfreek I've submitted the PR. I've detailed everything (I hope!) in the notes.

[drawbyperpetual]

@daverayment I like all the nice refactorings in your PR; I'll cancel mine - let's get behind yours!

[daverayment]

@daverayment I like all the nice refactorings in your PR; I'll cancel mine - let's get behind yours!

That's kind of you. Thank you very much.