dotnet / winforms

Windows Forms is a .NET UI framework for building Windows desktop applications.
MIT License
4.29k stars 956 forks source link

At 200% zoom buttons present under 'Remaining_Controls_Testing' are not visible: A11y_.NET CoreWinforms_MainForm_Zoom #11457

Closed PoojaNamde closed 2 weeks ago

PoojaNamde commented 1 month ago

.NET version

dotnet-sdk-9.0.100-preview.5.24258.1

Did it work in .NET Framework?

Yes

Did it work in any of the earlier releases of .NET Core or .NET 5+?

No response

Issue description

GitHub Tags:

A11yMAS; #A11yTCS; #A11ySev1; #BM_.NET Core[Winforms]_Win32_May2024; #.NETCore; #WCAG1.4.4; #DesktopApp; #Win11; #FTP; #Zoom;

Environment Details:

App name: .NET Core Winforms Window Version: Win 11 OS Build: 22621.3085

Prerequisites:

  1. Display resolution: 1280*768
  2. Scale-> Custom scaling 200%

Repro Steps:

  1. Launch the "Accessibility core app".
  2. Main Form screen would appear.
  3. Do the resize resolution and observe that At 200% zoom buttons present under 'Remaining_Controls_Testing' are not visible.

Actual Result:

At 200% zoom buttons present under 'Remaining_Controls_Testing' are not visible.

Similar issue is also observed in below scenario: Issue 1: ToolStripContainer_Bottomtool bar

  1. Launch the "Accessibility core app".
  2. Main Form screen would appear.
  3. TAB to "MenuToolbars_Controls:Testing the controls under Menu Toolbars Tab" and hit ENTER key.
  4. TAB to ToolStripContainer button and hit ENTER key.
  5. TAB to "Button1" present at the botoom
  6. Observe that at 200% zoom "Button1" present at the bottom is not visible.

Issue2: Print_ Preference

  1. Launch the "Accessibility core app".
  2. Main Form screen would appear.
  3. TAB to "Printing_Controls:Testing the controls under Printing Tab" and hit ENTER key.
  4. TAB to Print button and hit ENTER key.
  5. TAB to More setting button and hit ENTER key.
  6. "Printing Preference" Screen would appear.
  7. Observe that at 200% "Advance", "ok" and "Cancel" buttons are not visible.

Expected Result:

At 200% zoom buttons present under 'Remaining_Controls_Testing' should be clearly visible.

User Impact:

Low vision users will not be able to see the controls clearly and will not be getting information related to those.

Attachment

11457_A11y_ NET CoreWinforms_MainForm_Zoom

Issue1: 11457_Issue 1_ Toolstripcontainer

Issue2: 11457_Issue2_ Print_ Preference

Yash14j commented 1 month ago

GithubTags:#Rev:yaja;

MandiMan commented 1 month ago

This issue does not repro on screens with a display resolution of 3840x2160 and a scale of 200%. image image image

merriemcgaw commented 1 month ago

Also note that this is a Windows dialog not ours. This should fall under the Printing Dialog exception we already have.

PoojaNamde commented 4 weeks ago

@MandiMan Issue should be fixed for 1280 * 768 recommended display resolution as most of the users will be using this resolution. So could you fix it for and assign back to me.

merriemcgaw commented 3 weeks ago

@PoojaNamde this is a screen that is owned by Windows and we have no control over it. Previously we had been excluding certain printer related screens because we already have an exception. This should fall under the existing exception for Windows Printing APIs that we have.

PoojaNamde commented 3 weeks ago

@merriemcgaw, as per above comment as there is existing windows exception for printing screen, we will exclude that issue from this bug. Could you please fix other two issues mentioned in the bug.

merriemcgaw commented 2 weeks ago

@PoojaNamde ack! I didn't see the first requirements in the steps.

@Olina-Zhang can your team address these issues? Please go through the app and make changes where necessary to support (in System Aware) 200% scaling at the display and scale size mentioned in the prerequisites. You can add new screens and/or tabs to make sure everything fits the way it should. I think there are a few screens where we should do stuff.

Olina-Zhang commented 2 weeks ago

@PoojaNamde have updated and uploaded that app, please test it again. Thanks!

PoojaNamde commented 2 weeks ago

Closed; #Regressed:06-20-24;

Verified this issue in the latest environment, issue is fixed hence closing the bug.

Screenshot (1106) Screenshot (1107)