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

Keyboard focus color contrast with background color is 2.379:1 on Calander control and control present inside Calander popup: A11y_Azure Tools Storage Explorer_Manage Stored Access Policies_Nontext Contrast #8411

Open
3 tasks done
kapilvaishna opened this issue Jan 1, 2025 · 8 comments
Assignees
Labels
:accessibility: accessibility Related to accessibility :accessibility: sev1/2
Milestone

Comments

@kapilvaishna
Copy link

kapilvaishna commented Jan 1, 2025

Preflight Checklist

Storage Explorer Version

1.36.2

Architecture

x64

Platform

Windows

OS Version

Windows11

GitHub Tags:

#A11yMAS; #A11yTCS; #Win32; #DesktopApp; #A11ySev2; #BM_AzureToolsStorageExplorer_Win32_Dec2024; #Azure Tools Storage Explorer; #Devtools; #WCAG1.4.11; #FTP; #A11yWCAG2.1;

Environment Details:

Application: Microsoft azure storage explorer
Version: 1.36.2
OS: Windows 11 Enterprise 24H2
Build: 26100.2605

Repro Steps

  1. Launch Azure Storage Explorer application.
  2. TAB till "Account Management" in left Navigation and press ENTER key.
  3. TAB till any "Subsection" for example 'azure tools Manual testing 1' and select it.
  4. TAB till "Open explorer" button and press ENTER key
  5. "Explorer" section will open. TAB till selected subscription and expand it
  6. TAB till storage account and expand it.
  7. TAB till any storage account and expand it.
  8. TAB till "Blob Containers" and press ENTER key to expand it.
  9. TAB till any "Blob container" and press ENTER key to select it now right click and press down arrow key to "Mange stored access polices" and press ENTER key.
  10. TAB till "Add" button and press ENTER key.
  11. TAB till "calendar" button and Press ENTER key
  12. Observe that keyboard focus color contrast with background color is 2.379:1 on Calander control and control present inside Calander popup.

Actual Experience

Keyboard focus color contrast with background color is 2.379:1 on Calander control and control present inside Calander popup.

Similar issue observed in following scenario

  1. Blob Container_Table

Expected Experience

Keyboard focus color contrast with background color should be equal or greater than 3:1.

User impact

Low visibility user will face difficulty to see the keyboard focus.

Attachment

Image

Similar issue
Image

@InduPriya1805
Copy link

rev:inse

@craxal
Copy link
Contributor

craxal commented Jan 6, 2025

@kapilvaishna The calendar control is a system-rendered control, and we have no control over it. We would need to open a bug against Chromium.

@craxal craxal added the :accessibility: sev1/2 label Jan 6, 2025
@craxal craxal added this to the 1.38.0 milestone Jan 6, 2025
@kapilvaishna
Copy link
Author

@craxal I have dropped mail to chromium edge team to log external bug, as per the external bug process, Once the external bug is fixed and closed, we will verify and close this issue.

SL:External to chromium Edge:01-08-25

@kapilvaishna
Copy link
Author

@craxal we got the response from external team for then issue is not repro for below version

2nd issue Not Repro:
Win11:
OS Version: 24H2
OS Build: 26100.1742
Edge Canary Browser: 133.0.3061.0

Image

@craxal
Copy link
Contributor

craxal commented Jan 9, 2025

We have recently released 1.37.0, which includes an update to Electron and Chromium. Can you verify against that version?

@kapilvaishna
Copy link
Author

I have verified the issue in 1.37.0, it is reproducing

Image

Image

Image

@craxal
Copy link
Contributor

craxal commented Jan 10, 2025

@kapilvaishna Changes are not available in any public releases yet. Please wait for a new build from us.

@craxal craxal added the :accessibility: accessibility Related to accessibility label Jan 10, 2025
@craxal craxal self-assigned this Jan 14, 2025
@craxal
Copy link
Contributor

craxal commented Jan 14, 2025

@kapilvaishna Based on what you've told us, the bug is in Chromium and has been fixed in v133. That version is not yet available in generally available releases, either in Edge (it's still in Canary) or in Electron. The latest version of Electron (34) is using Chromium 132. We will not be able to fix this until a future Electron update. Therefore, we will not be able to fix this bug within the 60-day window.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:accessibility: accessibility Related to accessibility :accessibility: sev1/2
Projects
None yet
Development

No branches or pull requests

3 participants