[Image Resizer]: 'Image Sizes', 'Encoding' and similar headings are not announced by Narrator when focus moves to the first interactive element under them as they are not associated #13451
Labels
A11yE+D
Accessibility Team tag- issues found by Accessibility E+D team at Microsoft
A11ySev2
Accessibility team tag - P2 items
A11yTTValidated
Accessability team tag
A11yWCAG
Accessibility Team tag - Web Content Accessibility Guidelines
Area-Accessibility
Issues related to accessibility
Issue-Bug
Something isn't working
Resolution-Fix Committed
Fix is checked in, but it might be 3-4 weeks until a release.
Microsoft PowerToys version
0.45.0
Running as admin
Area(s) with issue?
ColorPicker, FancyZones, Image Resizer, Keyboard Manager, PowerRename, PowerToys Run, Shortcut Guide, SVG Preview
Steps to reproduce
Test Environment:
OS: Windows 11 Version Dev (22454.1000)
App version: 0.45.0
App name: Power Toys
Screen Reader: Narrator
Repro Steps:
Note:
Same issue is repro throughout the application. Hence, a global issue on this application.
User Impact:
If headings are not clear and descriptive, it would be difficult for screen reader dependent users to find the information they seek , and cannot understand the relationships between different parts of the content. Also if headings are not associated with the first controls under them the screen reader dependent user will not understand under with section of the page content the control lies.
Guideline Reference:
https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.html
WCAG.2.4.6.-.Image.Sizes.Encoding.and.similar.headings.are.not.announced.by.Narrator.when.focus.moves.to.the.first.interactive.element.under.them.as.they.are.not.associated.mp4
✔️ Expected Behavior
'Image Sizes', 'Encoding' and similar headings should be announced by Narrator when focus moves to the first interactive element under them, and they need to be associated with the first control.
❌ Actual Behavior
'Image Sizes', 'Encoding' and similar headings are not announced by Narrator when focus moves to the first interactive element under them as they are not associated. Hence a screen reader dependent user will not understand that under which section of the page the control lies within.
Other Software
No response
The text was updated successfully, but these errors were encountered: