Windows High Contrast Mode disabled input with border contrast bad [Accessibility] [A11y]
Categories
(Core :: Layout, defect, P3)
Tracking
()
| Accessibility Severity | s3 |
People
(Reporter: soro, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(1 file)
|
12.50 KB,
image/png
|
Details |
Screen Shot 2021-04-05 at 6.29.15 PM.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36
Steps to reproduce:
Turn high contrast mode on in Windows.
Visit the dat url data:text/html,<html><input disabled style=" border: none; " value=hi>
Found in both 78.6.1esr 64 bit and 84.0.2 64 bit
Actual results:
Notice that the text is green and the background is white. Not enough contrast. Background should be black which is what happens if you don't set border:none.
All border styles on disabled input cause this same issue. This is an accessibility issue.
Expected results:
Background should have remained black. If the border was set it should have surrounded the element rather than turning the inside white.
I would suspect this happens in all versions of windows 10 but just in case it turns out relevant:
Edition Windows 10 Enterprise
Version 20H2
Installed on 3/18/2021
OS build 19042.867
Experience Windows Feature Experience Pack 120.2212.551.0
|
||
Comment 2•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Accessibility Tools' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Edit: updated to 87 (64 bit), this still happens.
Also read up on new profiles. I was doing this in the default profile, but making a new profile and running (I tried in safe mode to make sure all addons were disabled) still triggers this issue
Edit: also happens with <textarea>s (again in high contrast mode)
data:text/html,<textarea style="border:none;" disabled>hi</textarea>
|
||
Comment 5•3 years ago
|
||
Not DevTools related.
I see that High Contrast mode issues are often handled in Core -> Layout.
Tentatively moving the bug there?
|
||
Updated•3 years ago
|
|
||
Updated•3 years ago
|
|
||
Updated•11 months ago
|
Description
•