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

[release/8.0]: Backport accessibility fixes into 8.0 #3486

Merged
merged 4 commits into from
Apr 9, 2024

Conversation

adamint
Copy link
Member

@adamint adamint commented Apr 8, 2024

Backports #3192, #3406, #3368, and #3189

Customer Impact

#3192 makes copy buttons inside data grids accessible to keyboard-only users. The workaround for them without this pull request is to manually select the entire cell's contents.

#3406 makes the log level select on StructuredLogs pages accessible to users with high resolution + high zoom. The element is inaccessible to them without that change.

#3368 Prevents focus state from being lost when closing a details panel manually. Otherwise, keyboard/screen-reader users will be confused when focus is removed from the page after closing the panel.

#3189 Modifies the reconnection UI to allow users to interact with on-screen elements.

Testing

Manual verification. See demo below (first #3192, then #3368, then #3189 at the end):

Animation

Risk

Low

Microsoft Reviewers: Open in CodeFlow

dotnet#3189)

* Avoid reconnection modal taking up entire screen, not being able to interact with page

* add slight padding, shadow

---------

Co-authored-by: Adam Ratzman <[email protected]>
(cherry picked from commit 87fab1e)
Co-authored-by: Adam Ratzman <[email protected]>
(cherry picked from commit 5a6856d)
* Re-focus button when closing details panel

* Add internal id for log entries, make sure to null element id on detail view closed

* Make sure view button is selected only after a user action

---------

Co-authored-by: Adam Ratzman <[email protected]>
(cherry picked from commit e784c91)
@dotnet-policy-service dotnet-policy-service bot added the Servicing-consider Issue for next servicing release review label Apr 8, 2024
@danmoseley danmoseley added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Apr 8, 2024
@RussKie RussKie merged commit 0ae12fd into dotnet:release/8.0 Apr 9, 2024
8 checks passed
@danmoseley danmoseley mentioned this pull request Apr 12, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-dashboard Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants