-
Notifications
You must be signed in to change notification settings - Fork 297
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
[DOCS]: Insufficient Color Contrast for clear button in docs search input #4749
Comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
PWABuilder issue fixed. Docs issue comes from a third party plugin |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
3 similar comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
1 similar comment
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
fixes #4750 fixes #4749 fixes #4754 ## PR Type <!-- Please uncomment one ore more that apply to this PR --> <!-- - Bugfix --> <!-- - Feature --> <!-- - Code style update (formatting) --> <!-- - Refactoring (no functional changes, no api changes) --> <!-- - Build or CI related changes --> <!-- - Documentation content changes --> <!-- - Sample app changes --> Other... Please describe: Accessibility fixes Also added typescript as a dependency to fix a build issue with npm start + updated shoelace to the latest version ## PR Checklist - [ ] Test: run `npm run test` and ensure that all tests pass - [ ] Target main branch (or an appropriate release branch if appropriate for a bug fix) - [ ] Ensure that your contribution follows [standard accessibility guidelines](https://docs.microsoft.com/en-us/microsoft-edge/accessibility/design). Use tools like https://webhint.io/ to validate your changes. ## Additional Information
Closed with the above PR |
What happened?
The color contrast analyzer indicates that the Close icon button on the Share score dialog has a contrast ratio of 2.1:1, which is below the recommended 3:1 for non-text graphical elements.
How do we reproduce the behavior?
Repro Steps:
What do you expect to happen?
Color should be within standard guidelines
What environment were you using?
Test Environment:
OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.461)
Edge Browser: Version 123.0.2400.1 (Official build) dev (64-bit)
URL: https://docs.pwabuilder.com/#/
Tool: Color contrast Analyzer
Additional context
User Impact:
Users with visual impairments, such as low vision or color blindness, may struggle to perceive or locate the Close icon button on the Share score dialog due to inadequate color contrast.
WCAG Reference:
https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast
Attachments:
![CCA fails for search clear button](https://private-user-images.githubusercontent.com/117908911/341470394-7de36389-c06f-4f7f-9c2b-86f35f8f5f0b.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1MTEyNzIsIm5iZiI6MTczOTUxMDk3MiwicGF0aCI6Ii8xMTc5MDg5MTEvMzQxNDcwMzk0LTdkZTM2Mzg5LWMwNmYtNGY3Zi05YzJiLTg2ZjM1ZjhmNWYwYi5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNFQwNTI5MzJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05YzViMjJhMDczOTQxZGUxYWI5ZGFhNTkyMmNiYjZiNzAyNzdmNzI1YTZlZjVjNmM1NzVmZDYzZmE5MDVmYWUwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.yUDmyzZRI_Grau7FEbH8mC9S13gXykR94JGjjdkDilk)
The text was updated successfully, but these errors were encountered: