Fix keyboard focus order in the SDK installer#55813
Conversation
|
Azure Pipelines: 3 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Co-authored-by: nagilson <23152278+nagilson@users.noreply.github.com>
|
There might be fallout here around accessibility and screen readers. This will require handing off a private build for assessment to ensure nothing is being regressed. |
|
The Installation Successfully Completed text is not read out loud by Narrator. Verified against 10.0.400 that the text is being read. I reached out to the CAI channel - the code change is fine. Pretty sure we fixed this during the AI pass in 10 when the text wasn't being read, so this fix would technically be a regression. We can have one or the other, but not both. |
joeloff
left a comment
There was a problem hiding this comment.
LGTM, I verified they layout on non-ENU locales too like German (1031). CAI chat suggests the unnecessary tab may be considered higher impact, especially for users that navigate through voice.
The installer placed keyboard focus on a static success heading and announced descriptive content with the “Learn more” link.