Improve screen reader, keyboard, and High Contrast accessibility - #2518
Open
jbgrimsby wants to merge 1 commit into
Open
Improve screen reader, keyboard, and High Contrast accessibility#2518jbgrimsby wants to merge 1 commit into
jbgrimsby wants to merge 1 commit into
Conversation
jbgrimsby
marked this pull request as ready for review
August 18, 2026 17:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This change corrects screen-reader and keyboard interaction in the Start Menu, Classic Explorer, and Classic IE settings dialogs while preserving the existing visual workflow.
It also makes the new-application indicator respect the Windows High Contrast palette, addressing the color conflict described in #2054.
What changed
modifiedonly when a setting differs from its default, matching the existing bold visual treatment.Root cause
The settings interface visually represented checkbox, radio-button, selected, default, and modified states through custom tree images and bold text, but exposed the items to assistive technology as generic outline items. Some keyboard behavior was also implemented differently from standard Windows tree and property-page interaction.
The new-application indicator could additionally use a skin foreground color as a background under High Contrast, producing unreadable adjacent items.
Validation
CallCancelledexception occurred during that run. This single run is positive evidence but does not claim that the separate intermittent report is conclusively resolved.User impact
Screen-reader users can determine which settings are selected or modified, navigate the trees using standard Windows conventions, and move through the dialogs in a predictable order. Sighted users retain the existing layout, bold modified-setting indication, and normal theme rendering.