#92625Form elements have insufficient color contrast and focus style
Description
The form elements do not have sufficient contrast for users with a visual impairment. A contrast of 3:1 for input fields and buttons is required, as long as there is no sufficiently contrasted icon (3:1) or text (4,5:1) element placed inside. The contrast can be measured border and fill or border and background.
Reproduction steps
- Use colour contrast analyser
- Measure contrast (between border/fill or border/background)
Impact
Target group
visual
Severity
high
Frequency
very common
Definition of Done
WHEN I measure contrast of input field or button (without text or icon inside) against background or fill, the contrast is at least 3:1 or more
Recommended solution
enhance contrast of border
References / WCAG 2.2 Reference
1.4.11
Prioritizing the removal of the issues found
must have
Screencast or Screenshot
clipboard-202510161550-nk2ko.png
—-
Original Ticket Text:
The form elements in the Edit section have the border color #bbb. When the form elements receive focus, the border color is #aaa. Both of those colors surrounded by the background color #ededed have an insufficient contrast ratio of 1.98:1, see WebAIM Color Contrast Checker
When the form elements receive focus, the elements get a subtle box-shadow and the border-color changes from #bbb to #aaa, which is an insufficient contrast change from 1.21:1, see WebAIM Color Contrast Checker
Reviews 2
History 713
-
Mylene Kreiger changed Tags
accessibilityaccessibility, tas2020 <span data-processor="relativetime" data-value="2020-10-22T13:33:04+00:00" > 10/22/20, 13:33 </span> -
Riccardo De Contardi changed parent task #89595 <span data-processor="relativetime" data-value="2020-10-24T17:49:59+00:00" > 10/24/20, 17:49 </span>
-
Gerrit Code Review pushed patch set 1 for master to change 66873 status
NewUnder Review <span data-processor="relativetime" data-value="2020-11-23T19:54:58+00:00" > 11/23/20, 19:54 </span> -
Gerrit Code Review pushed patch set 2 for master to change 66873 <span data-processor="relativetime" data-value="2020-11-23T19:56:28+00:00" > 11/23/20, 19:56 </span>
-
Gerrit Code Review pushed patch set 3 for master to change 66873 <span data-processor="relativetime" data-value="2021-05-04T12:13:15+00:00" > 05/04/21, 12:13 </span>
-
Gerrit Code Review pushed patch set 4 for master to change 66873 <span data-processor="relativetime" data-value="2021-05-04T18:05:58+00:00" > 05/04/21, 18:05 </span>
-
Daniel Goerz commented and changed status
Under ReviewNeeds Feedback <span data-processor="relativetime" data-value="2021-05-04T18:32:53+00:00" > 05/04/21, 18:32 </span> -
Gerrit Code Review pushed patch set 1 for main to change 91029 status
Needs FeedbackUnder Review <span data-processor="relativetime" data-value="2025-10-13T14:50:18+00:00" > 10/13/25, 14:50 </span> -
Gerrit Code Review pushed patch set 2 for main to change 91029 <span data-processor="relativetime" data-value="2025-10-13T15:10:34+00:00" > 10/13/25, 15:10 </span>
-
Markus Timtner changed Duplicated by #92671 <span data-processor="relativetime" data-value="2025-10-16T13:47:19+00:00" > 10/16/25, 13:47 </span>
-
Markus Timtner changed attached clipboard-202510161550-nk2ko.png description TYPO3 Version
1114 Tagsaccessibility, tas2020accessibility, tas2020, TAS2025 <span data-processor="relativetime" data-value="2025-10-16T13:50:56+00:00" > 10/16/25, 13:50 </span> -
Markus Timtner changed description <span data-processor="relativetime" data-value="2025-10-16T13:55:03+00:00" > 10/16/25, 13:55 </span>
-
Markus Timtner changed Complexity easy <span data-processor="relativetime" data-value="2025-10-16T14:11:01+00:00" > 10/16/25, 14:11 </span>
Can you please update the issue for current master? Things seem to have changed with the bootstrap update.