Opening Text and Layout drop-downs using keyboard navigation will show incorrect background color
Categories
(Toolkit :: Reader Mode, defect, P3)
Tracking
()
People
(Reporter: danibodea, Assigned: Gijs, NeedInfo)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(2 files)
Note
- When the user navigates to the Text and Layout panel and opens the drop-downs Font or Font Weight drop-downs using keyboard navigation, he will notice that a wrong background color is rendered for the drop-downs.
- A different background color is rendered when opening these drop-downs using cursor navigation. It appears as if the "hover-effect" color is shown when using the cursor and the "non-hover" color is shown when using keyboard navigation.
Found in
- Beta v129.0b2
Affected versions
- Nightly v 130.0a1
- Beta v129.0b3
Tested platforms
- Affected platforms: all
- Unaffected platforms: none
Steps to reproduce
- Load an article that supports Reader View.
- Enter Reader View mode.
- Using the cursor, navigate to Text and Layout panel and open the Font or Font Wieght drop-down. Then close it.
- Using keyboard navigation open any of the drop-downs.
Expected result
- An incorrect background color is displayed.
Actual result
- The same background color is displayed.
Regression range
- not a regression, since implementation.
Additional notes
- This issue occurs on all OSes, in all combinations of Browser Theme and Reader View Theme, but some are more obvious than others:
Browser Dark Theme + Reader View Auto - obvious
Browser Dark Theme + Reader View Light - obvious
Browser Dark Theme + Reader View Dark - obvious
Browser Dark Theme + Reader View Sepia - obvious
Browser Dark Theme + Reader View Contrast - obvious
Browser Dark Theme + Reader View Gray - obvious
Browser Light Theme + Reader View Auto - yes, but small difference
Browser Light Theme + Reader View Light - yes, but small difference
Browser Light Theme + Reader View Dark - obvious
Browser Light Theme + Reader View Sepia - yes, but small difference
Browser Light Theme + Reader View Contrast - obvious
Browser Light Theme + Reader View Gray - yes, but small difference
Comment 1•1 year ago
|
||
Marking access-s3. It looks like the incorrect background colors in the given example leave us with text color #F7FBFE on background #55555F, which is still passing WCAG AAA (at a ratio of 7.08). The more concerning thing about this from an accessibility perspective is what we're communicating - it seems that we're losing the info we try to communicate with hover state.
Comment 2•1 year ago
|
||
The severity field for this bug is set to S4. However, the accessibility severity is higher, .
:Gijs, could you consider increasing the severity?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Comment 5•1 year ago
|
||
| bugherder | ||
Updated•11 months ago
|
Updated•11 months ago
|
| Reporter | ||
Comment 6•11 months ago
|
||
I understand that the fix is supposed to make: "select dropdowns in reader mode use same background when focused or hovered".
The change seems somewhat unsatisfactory and I'll try to explain:
-
Affected Build Release v137.0.2 behavior:
Case A. Using mouse, click any drop-down: causes it to open with the background color same as hover color, showing no hover effect over the drop-down options.
Case B. Using mouse, open any drop-down, than the other one: causes the drop-down to open in a different color than the hover color, allowing the hover effect to work on the drop-down options.
Case C. Using keyboard, open any drop-down: causes the drop-down to open in a different color than the hover color, allowing the select effect to work on the drop-down options, just like a hover effect. -
Build containing the fix Beta v138.0 (RC) behavior:
Case A. behavior does not change.
Case B. behavior does not change
Case C. Using keyboard, open any drop-down: causes the drop-down to open in the same color as the hover color, disabling the select effect to on the drop-down options, just like a hover effect.
Conclusion: The behavior with Case B is more aesthetic, proving that there is an improved UI version of these drop-downs' behavior, giving the impression that the UI is not working properly in Case A and C, where there is no hover effect or keyboard selection effect.
Is there a reason why the change was not made the other way around? I would suggest that the behavior of Case A and C is made to match Case B. Meaning, the drop-down background color should NOT match with the hover color. This would enable the hover effect and select effect with keyboard navigation inside the drop-down in all 3 cases. Does this make sense? Thanks!
Description
•