Issue Bug Rejected

#108685Link Browser: Input field border has insufficient contrast

Christian Jung 01/19/26, 10:07 updated 02/05/26, 09:44

Description

In the “Link Browser” dialog, input fields (e.g., URL) are too faint. The border (#E1E1E1) against the surrounding background (#E6E6E6) achieves only a 1:1 contrast ratio. This fails WCAG 2.1 SC 1.4.11 (Non-text Contrast), which requires at least 3:1 (recommended ≥ 4.5:1). This impairs recognition and usability for users with visual impairments.

Reproduction Steps

Open TYPO3 backend and edit content with RTE/link functionality.
Insert/edit a link to open the “Link Browser” dialog.
Inspect an input field (e.g., URL) and test the border contrast with CCA.
Result: Border #E1E1E1 vs. background #E6E6E6 → contrast 1:1.

Impact

Low input field discoverability; increased error risk.
WCAG 2.1 SC 1.4.11 violation; accessibility and compliance risks.
Poor UX for users with low vision.

Recommended Solution

Increase the input field border color in the “Link Browser” to a darker tone so the contrast against the surrounding background is at least 3:1 (ideally ≥ 4.5:1).
Apply consistently for default, hover, focus, disabled, and error states.
Implement via central theme/SCSS variables (backend UI) rather than hard-coded values.
Respect system/high-contrast modes and re-validate with CCA/axe.

Definition of Done

Updated styles implemented, tested, and merged.
Contrast measurements show ≥ 3:1 across relevant states and themes.
No adverse side effects on other backend form controls.
Documentation/changelog note added.

Acceptance Criteria

Input field borders in the “Link Browser” achieve at least 3:1 contrast against the background (recommended ≥ 4.5:1).
Focus and hover states are also compliant (≥ 3:1).
Disabled and error states remain distinguishable and accessible.
Validation with Colour Contrast Analyser (CCA) and automated checks (e.g., axe) passes.
Functionality and layout remain intact in supported browsers.

References

WCAG 2.1 SC 1.4.11 Non-text Contrast: https://www.w3.org/TR/WCAG21/#non-text-contrast
Understanding Non-text Contrast: https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html

Reviews 2

Files 2

History 26

  1. Benjamin Franzke commented and changed status Under Review Rejected <span data-processor="relativetime" data-value="2026-02-02T11:18:38+00:00" > 02/02/26, 11:18 </span>

    Hi, thanks for you report.

    Input borders do not require to provide contrast, if the background of the input element has sufficient contrast to the background where it is displayed on.

    (Reminder: An input border – from an a11y perspective – exists to distinguish a white input on white ground, so it is only needed for the case where the background does not provide contrast on its own)

    Here’s a quote where this is officially described:

    https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html#adjacent-colors
    > Figure 3. Pass: The contrast of the input background (white) and color adjacent to the control (dark blue #003366) is sufficient. There is also a border (silver) on the component that is not required to contrast with either.

    I hope it’s OK that I close this ticket based on this WCAG statement.

    (Please also note that v14 changed the interface to use a white background instead of gray background)

  2. Philipp Tautz commented and changed attached Screenshot 2026-02-05 at 10.44.16.png <span data-processor="relativetime" data-value="2026-02-05T09:44:41+00:00" > 02/05/26, 09:44 </span>

    Hi Team, to follow up on Christians Ticket:

    In our installations we have the fields in the following contrast:

    1. Border (#BFBFBF) against grey background (#E6E6E6): 1.5:1
    2. Border (#BFBFBF) against white background (#fff): 1.8:1

    Screenshot attached. Neither would meet 1.4.11

    Please reopen the ticket and let me know what we could do about this.

    Thank you,

    Philipp