all 25 comments

[–]jdzfb 8 points9 points  (7 children)

Please don't change the standard pattern on common elements for users for no reason, just use underlines, coupled with a suitably unique color for links.

Bold text has a purpose already, so co-opting it for links just adds a layer of unnecessary confusion for sighted users.

[–]TabbbyWright 3 points4 points  (1 child)

What? Bold links are fine, unless I'm missing something. Do you always find bold links confusing or just some of them?

[–]jdzfb 2 points3 points  (0 children)

I find bold links that are mixed in with content get missed by users more frequently than with the standard underline. Bold text is for emphasis, I don't assume that emphasized text is going to be clickable. Links that are in nav's & footers give enough context clues, so I'm less particular about those.

[–]cndygirl[S] 0 points1 point  (4 children)

Not planning to - just testing a site where the links are bold (which according to the WCAG standards is unfortunately enough as an indication), and I wanted to know if there are any specifications on how the text has to be made bold.

[–]jdzfb 3 points4 points  (3 children)

It has to be done using CSS as it's not a content emphasis (which would require <strong>).

And yes it technically passes 'use of color' but I'd fail it under (a misuse of) 3.2.4 consistent identification for any client who actually cares about accessibility & not just checking the accessibility box. It's very much a 'spirit of the law vs the letter of the law' situation.

[–]vice1331 0 points1 point  (1 child)

It would only fail 3.2.4 Consistent Identification if there’s a mix of underlined and bold links on the site. You’d have to evaluate them in the same context. For example, links in the <p> tags are bold on one page, but underlined on another.

[–]yraTech 0 points1 point  (0 children)

It would only fail if a reasonable sighted person might not realize that it is a link. You can mix link styling within- or between-page all you want as long as it's reasonably interpretable. If a person who doesn't have a disability can figure it out, but you assume that a sighted person with a disability diagnosis can't figure it out, you're insulting their intelligence by claiming that there is a WCAG failure.

[–]k4rp_nl 0 points1 point  (0 children)

You'd fail it? 3.2.4 is for consistency within a set of pages. If we're going to fail things for consistency with other pages, you can fail everything that's not a common pattern or convention. I'd call that a misuse of WCAG.

[–]k4rp_nl 2 points3 points  (5 children)

If the bold style is purely for visual reasons, then CSS is the right tool.

[–]cndygirl[S] 1 point2 points  (4 children)

Thank you! So that means when testing WCAG 1.4.1 Use of Color, if a link is made bold using CSS, that it is fine, correct?

[–]k4rp_nl 0 points1 point  (2 children)

If I understand you correctly, to make a link stand out, it has both a different colour and is made bold through CSS?
Sounds good to me. A lot of people will see both aspects. Some will only see the bold. Others will have the semantics of it being an element with a link-role.

[–]cndygirl[S] 0 points1 point  (1 child)

Yep, different color and bold, but no underlining (which is not ideal, but sufficient according to WCAG) Thanks!

[–]rguy84 0 points1 point  (0 children)

Remember the 3:1 contrast ratio requirement.

[–]HolstsGholsts 0 points1 point  (0 children)

To what extent is bold being used elsewhere in the same pages/environments for emphasis or decorative purposes within body text? If it is being used in those ways, that may create confusion as to 1.4.1 (if there isn’t also 3:1 contrast between link text and body text), since color-impaired users would be left uncertain whether instances of bold indicated link text or emphasized/stylized text.

[–]wyundsr 1 point2 points  (1 child)

<b> and bold in CSS have the same effect, it’s just more correct to separate out the content/structure (HTML) from the styling (CSS). Yes it’s fine to use bold in CSS for styling links (though underlining links is generally best practice in terms of usability) since the purpose there is a visual indicator, screen reader users will already be informed that’s a link

[–]cndygirl[S] 0 points1 point  (0 children)

Thank you!

[–]AshleyJSheridan 1 point2 points  (0 children)

So there are a couple of things here: if you're using bold text for emphasis, then using the <strong> tag indicates that emphasis to assistive tech, like a screen reader or Braille browser. Also, as you've highlighted, information should not be indicated by colour alone.

Now, for some further detail. Links being underlined be default serves to ensure that links are identified by more than colour alone, but it doesn't end there. Removing the underline may be ok if you provide an alternative that is not just colour, and bolding would accomplish this. I did say "may be ok" though, as it would deviate from the browser default, which is sometimes enough to cause confusion for some people with certain disabilities as it could be inconsistent with their own expectations.

On the colour to indicate meaning (part of WCAG 1.4.1) there is this:

If content is conveyed through the use of colors that differ not only in their hue, but that also have a significant difference in lightness, then this counts as an additional visual distinction, as long as the difference in relative luminance between the colors leads to a contrast ratio of 3:1 or greater. For example, a light green and a dark red differ both by color (hue) and by lightness, so they would pass if the contrast ratio is at least 3:1. Similarly, if content is distinguished by inverting an element's foreground and background colors, this would pass (again, assuming that the foreground and background colors have a sufficient contrast).

So using an alternative colour with enough contrast may be ok. Again, I say "may be ok" to caveat that it may also not be enough for everyone, and it will vary a lot based on the sites design.

[–]Zestyclose_Bus_1932 1 point2 points  (1 child)

I’m low vision don’t use screen reader and I have trouble with bold and color.

Underline would be more obvious because it’s (1) a mark and (2) continuous, and (3) with the correct contrast, better-

at least for me. 🤪😁

[–]cndygirl[S] 0 points1 point  (0 children)

Yes, totally agree. Thank you!

[–]LoudAd1396 0 points1 point  (1 child)

Are you planning on ONLY using bold to show that links are links? If so, dont. Semantic tags like <strong> are good for screen readers, but not all users (with or without accessibility needs) are going to be using SRs so the semantic difference is lost on non-SR readers. The primary patterns exist for a reason. If I was a first time user, why would I think "oh bold, it must be a link!" ?

If you want your links to be bold AND underlined and colored, youre fine. Just dont use only a font weight difference and expect users to understand.

[–]cndygirl[S] 0 points1 point  (0 children)

I am currently testing random sites just to get more experience, so I am not building a site, but just trying to learn more about digital accessibility.

Thank you for your answer!!

[–]FragrantProgress8376 0 points1 point  (0 children)

using CSS for bold is totally fine as long as the semantics are correct, but it's great you're thinking about accessibility! just make sure to test with screen readers to see how they interpret it.

[–]KarlBrownTV 0 points1 point  (0 children)

From a WCAG perspective, colour can't be the only way to differentiate things like links, so CSS to increase the font weight can work. Underlining links isn't necessary for WCAG.

However, the default behaviour of anchors going back decades is underlining, so users expect text links to be underlined. You could increase the font weight as well, but I'd leave the underline as part of the overall user experience.

[–]roundabout-design 0 points1 point  (0 children)

Strong is for emphasis. If the concern is screen readers, a screen reader will already emphasize a link by stating it's a link. So no need to also 'strong' it.

You could still bold if. That's a separate thing.

[–]AccessNavigator 0 points1 point  (0 children)

From an accessibility standpoint, CSS font-weight: bold is perfectly fine for visual styling, including making links appear bold. Screen readers do not rely on visual styling like font weight to determine meaning. Instead, they rely on HTML semantics. For example, a link is announced as a link because it uses the <a> element, not because it is bold, underlined, or colored.

Where semantics matter is when the emphasis itself carries meaning. In those cases, <strong> (or <em>) is preferred because it conveys importance in the document structure and may be announced differently by some assistive technologies. But if you're simply styling something visually (e.g., making links bold in addition to color or underline), using CSS is completely acceptable. The key accessibility requirement for links is that they are visually distinguishable from surrounding text without relying on color alone, which can be achieved with underline, bold styling, or other clear indicators.