[Bookmarks Evolution] Selected state checkmark and header text and icon buttons have low color contrast
Categories
(Firefox for Android :: Bookmarks, defect)
Tracking
()
People
(Reporter: ayeddi, Assigned: fmasalha)
References
(Blocks 1 open bug)
Details
(Keywords: access, good-first-bug, Whiteboard: [fxdroid][group1])
Attachments
(2 files)
Steps to reproduce
- Open Firefox and navigate to the Settings > Bookmarks menu
- Select a directory or a bookmark by a long-tap on it
- Observe the visual appearance of the selection mode on Bookmarks
Expected behavior
- All essential parts of UI (all text and each meaningful image like an icon for an image button) are readable and easy to discern.
Actual behavior
access-S2
item:X Selected
text in the selected header - 3.11:1 color contrast for the white on purple is not sufficient, 4.5:1 or higher is expected.access-S4
items: Image buttons like a checkmark next to the selected item, and selected header's Back, Edit, Move, More options have color contrast that is WCAG-compliant (3.11:1 while 3:1 is the minimum requirement by the WCAG 2.2 for an essential graphics) but it is hard to discern.- Note: Similar issue is reported in bug 1883627. In both cases there is some text (
X selected
) involved, thus a text contrast is required to be 4.5:1 or more in color contrast for readability in WCAG 2.x. But it would improve the experience for the non-text essential graphics (like icon buttons) as well:- Foreground: #FFFFFF
- Background: #AB71FF
- The contrast ratio is: 3.2:1 (3.11:1)
- 1.4.3 Contrast (Minimum) (AA)- Fail for regular text
- 1.4.11 Non-text Contrast (AA) - Pass for UI components and graphical objects (passing at 3:1 which is very close to the current color combination)
- Remediation note: using the same darker purple shade #7541E5 as is used in the Search button would provide sufficient for WCAG compliance color contrast of 5.8:1 for both text and graphics.
Device information
- Firefox version: Firefox Nightly 139.0a1 (build #2016084991)
- Android device model: Samsung Galaxy A54 5G
- Android OS version: 14
Any additional information?
refer to the notes in the Actual behavior above
Updated•6 months ago
|
Updated•6 months ago
|
Comment 1•6 months ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:boek, could you consider increasing the severity?
For more information, please visit BugBot documentation.
Comment 2•5 months ago
|
||
Refer to Figma for mobile color styles. These are accessed in Fenix through FirefoxTheme. This uses AcornTheme under the hood, which can also be used if ever writing code in A-C. When in doubt, #firefox-mobile-eng-ux and #mobile-android-team can be good resources to ask.
Comment 3•2 months ago
|
||
It seems that this may be a design-system-level fix, so I have mentioned this in #firefox-mobile-eng-ux and asked for some guidance on what to do.
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 4•2 months ago
|
||
Hi team,
I took a look into this and it looks like if we remap the colors to M3 tokens, we can resolve this! :)
We would need to make a few modifications to: page background, top app bar default state, top app bar selected state, text/icons default state, and text/icons selected state.
The changes are the following:
Element | Current | Remap |
---|---|---|
Page background | layer1 | Surface |
Default: Top app bar | layer1 | Surface |
Default: Text & icons | Text (textPrimary), Icons (iconPrimary) | On Surface |
Selected: Top app bar | layerAccent | Primary |
Selected: Text & icons | textInverted | Inverse on Surface |
Here is a reference to the M3 color mapping:
https://www.figma.com/design/MjufE1X5fvkxZ0YneX4kRd/Android-Library--2025-?m=auto&node-id=64745-6578&t=vye0HL84LXTUAYLb-1
and a reference to the design:
https://www.figma.com/design/n6pHx1rvt7iTMPzby250gL/M3-redesign-references?node-id=31-5676&t=atD1MW4RXK2CXMxp-1
Let me know if you have any questions, thanks!
Updated•2 months ago
|
Comment 7•2 months ago
|
||
bugherder |
Updated•2 months ago
|
Description
•