[a11y] Consider increasing the "Block audio only" text foreground to background contast ratio in Private browsing
Categories
(Firefox for Android :: Privacy, defect)
Tracking
()
People
(Reporter: apetridean, Assigned: rebecatudor273)
References
Details
(Keywords: access, Whiteboard: [fxdroid])
Attachments
(3 files)
Steps to reproduce
- Have the Accessibility scanner installed and opened.
- In PM, navigate to a website (e.g. www.cnn.com)
- Tap on the lock icon and, then scan the page.
- Tap on the "Block audio and video" arrow.
- Using the Accessibility Scanner, scan the page.
Expected behavior
No suggestions are made.
Actual behavior
-
Consider increasing this item's text foreground to background contrast ratio.
Current: 4:36::1. Foreground: #AA70FF
Suggested: 4:50:1 Background: #321C64 -
After tapping the arrow : for "Allow audio and video" -Current: 4:07:1. Foreground: #AA70FF
Suggested: 4:50:1 Background: #303030
for "Block audio and video" -Current: 4:18::1. Foreground: #AA70FF
Suggested: 4:50:1 Background: #2E2E2E
for "Block audio only" -Current: 4:07::1. Foreground: #AA70FF
Suggested: 4:50:1 Background: #303030
Device information
- Firefox version: Firefox130.0b9
- Android device model: Google Pixel 7 Pro (Android 14)
| Reporter | ||
Comment 1•1 year ago
|
||
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Privacy' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•1 year ago
|
||
Insufficient color contrast is an access-S2 issue that makes this part of the UI inaccessible for users with low vision, users with cognitive disabilities, users with dyslexia, with colorblindness, users with screen glare, etc.
We need to ensure that color contrast of the foreground against background of at least 4.5:1 in luminosity ratio is provided to comply with the minimum WCAG 2.x criterion, color contrast of 7:1 is recommended.
While in this case the color contrast is 4.18:1 which is getting close to the 4.5:1 threshold, it is still hard to read and it would still be flagged by all automatic testing tools, thus marking it as access-S2 nevertheless.
Comment 4•1 year ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:Gela, could you consider increasing the severity?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 5•1 year ago
|
||
Previously it was used accentUsedOnDarkBackground which was using
for private mode accent_high_contrast_private_theme.
Comment 7•11 months ago
|
||
| bugherder | ||
| Assignee | ||
Updated•11 months ago
|
Comment 8•11 months ago
|
||
Verified as fixed in Nightly 139.0a1 from 04/14 with Google Pixel 8 Pro (Android 15). There no recommendations related to background contrast ratio made anymore.
Updated•11 months ago
|
Comment 9•11 months ago
|
||
The patch landed in nightly and beta is affected.
:rebecatudor273, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox138towontfix.
For more information, please visit BugBot documentation.
Comment 10•11 months ago
|
||
:Gela looks like rebecatudor273 is out, can you confirm this will not be uplifted to 138?
Comment 11•11 months ago
•
|
||
I don't think we have any plans to uplift this to 138, I've updated the 138 status.
Comment 12•11 months ago
|
||
no convos just following up before RC week. Thank you!
Updated•11 months ago
|
Description
•