In one paragraph
Links must be distinguishable without relying on color addresses inline navigation that users may not recognise from hue alone. A persistent underline is often a robust approach, while significant lightness contrast or other effective cues can also matter under the applicable guidance. Inspect the actual context and all states. A resting-state automated pass does not certify complete link usability, text contrast, or keyboard focus visibility.
Why it matters
Colour hue alone can be an unreliable signal. Differences in relative luminance, text decoration, shape, or other effective presentation can help convey that words are interactive. Do not reduce the requirement to a universal rule that every link must be blue or every site must use one visual treatment.
A 3:1 link-to-surrounding-text comparison is different from the contrast between text and its background. Passing one does not automatically satisfy the other. Appropriate text contrast and visible keyboard focus still need their own assessment.
The current W3C guidance recognises a sufficient lightness distinction; do not turn an older technique description into an unsupported claim that colour hue alone with any hover effect is always enough. Persistent underlines can avoid ambiguity without relying on users first discovering the link by pointer movement.
How WebAuditOS evaluates this finding
The supplied link-in-text-block rule inspects selected visible inline links inside qualifying text blocks and compares them with the nearest block-level ancestor, not necessarily the immediately adjacent styled words.
It accepts its documented contrast or style-difference paths and sends some uncertain colour or generated-content cases to review. Serious impact maps to high severity. Resting-state inspection does not exercise hover and focus, and a same-colour or font-difference exception is not proof that users recognise every accepted candidate as a link.
How to fix it
- Identify links embedded in running text and inspect how their presence is communicated before interaction. Menus or standalone controls need an appropriate design too, even when this rule excludes them.
- Prefer a clear persistent cue where practical. For example:
.article a { text-decoration: underline; text-underline-offset: 0.15em; }This styling does not choose accessible colours or complete focus behaviour. Test the actual links and surrounding typography.
- If relying on another cue, verify it is sufficient and noticeable under applicable guidance. A tiny weight difference accepted by a heuristic may not be obvious in the real font or device.
- Measure link-to-text contrast separately from each foreground-to-background ratio. Check the actual local context, including spans, emphasis, themes, opacity, and background variations.
- Test visited, hover, focus, active, and disabled-like states where relevant. Do not remove focus indicators as part of making underlines look tidier.
- Check text over images, gradients, and generated decorative content manually. A needs-review result omitted from a violations-only report is not a pass.
- Review native href behaviour, descriptive link names, keyboard operation, zoom, and touch. A visual cue does not make a broken or misleading destination usable.
- Rescan and inspect representative prose, cards, footers, and responsive styles. Treat rule exclusions as coverage boundaries rather than an instruction to stop communicating interactivity elsewhere.
What the fix can break
A global underline can affect buttons styled as links, icons, and navigation aesthetics. Scope rules deliberately without making ordinary body links ambiguous again.
Colour changes can fix link separation while reducing background contrast. Measure the complete combination in every theme.
Do not assume a link is recognisable because a screenshot shows a subtle font or background difference. Test normal reading and the actual rendered styles.
Questions
Is the 3:1 ratio against the background?
For the link-distinction path discussed here, it is against surrounding non-link text. Background text-contrast requirements are separate.
Must every link use an underline?
Not universally, but persistent underlines are often a straightforward robust cue for prose links.
Does a resting-state pass validate keyboard focus?
No. Focus visibility and operation require additional testing.
Which related checks help?
Review text contrast, link names, and the automation limits guide.
What severity does this get in the report?
High. An axe finding takes its severity from the impact axe reports for the element that failed, and the report maps critical and serious to high, moderate to medium, minor to low. This rule is declared serious in axe-core 4.13.0, so every failure arrives as high.